Update message when keys are NOT being injected#3799
Conversation
|
@blueorangutan package |
|
@andrijapanicsb a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-563 |
|
@blueorangutan test centos7 vmware-65u2 |
|
@andrijapanicsb a Trillian-Jenkins test job (centos7 mgmt + vmware-65u2) has been kicked to run smoke tests |
|
Trillian test result (tid-742)
|
|
2020-01-10 00:06:19,449 DEBUG [c.c.s.ConfigurationServerImpl] (DirectAgent-5:ctx-2e05c809 10.2.2.71, job-1/job-27, cmd: StartCommand) (logid:1686008a) Executing: /bin/bash /usr/share/cloudstack-common/scripts/vm/systemvm/injectkeys.sh /var/cloudstack/management/.ssh/id_rsa.pub /var/cloudstack/management/.ssh/id_rsa /usr/share/cloudstack-common/vms/systemvm.iso Looks good. |
DaanHoogland
left a comment
There was a problem hiding this comment.
just messages improved. log scrapping might be impacted but in this case it should IMNSHO
|
Merging based on 2 x LGMT/approval and automated tests passing, and manual testing (by me). |
* Update message when keys are NOT being injected * Correct the message after injectkeys.ssh is done * Update message to a more meaningful one, since sometimes nothing is injected * Update other 2 * typo
Description
When the injectkeys.sh script runs, if the public ssh key is the same as the authorized_keys file inside the extracted systemvm.iso - then the public ssh key files is NOT copied over and the systemvm.iso is not modified - message added to explain just that.
Also, after the injectkeys.sh is run/finished, from the Java code we currently generate a wrong message that the private key has also been injected (we don't inject it, only the public key) - and in general sometimes NOTHING is injected - so changed the messages accordingly.
Types of changes
How Has This Been Tested?
Restarted the mgmt server for an existing installation, injectkeys.ssh was run, and confirmed that the systemvm.iso is NOT modified, same modification date, same md5sum as before.
Message properly logged in the mgmt logs, as follows: