[
https://issues.apache.org/jira/browse/CLOUDSTACK-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508351#comment-13508351
]
Marcus Sorensen commented on CLOUDSTACK-577:
--------------------------------------------
The way this should work if I remember correctly is that the keys are copied to
the system VM patch disk, then the patch disk is attached as /dev/vdb and the
system vms startup scripts then copy the keys into root's authorized keys file.
I would be interested in which part of this process is not working for your
environment if you can troubleshoot given that info, since it otherwise works
in the KVM installations we've done. In the past this has been seen due to a
missing systemvm.iso as the startup script looked for one (even though it
wasn't necessary).
> CS4 System VMs not patching
> ---------------------------
>
> Key: CLOUDSTACK-577
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-577
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, VNC Proxy
> Affects Versions: 4.0.0
> Environment: Ubuntu 12.04 Management Server. Ubuntu 12.04 Host,
> Qemu-KVM 1.0, Libvirt 0.10.2.
> Cloudstack 4.0.0-incubating.20121024195401
> Reporter: Trevor Francis
> Priority: Blocker
> Fix For: 4.0.0
>
>
> New system installed via apt-get cloud-client and cloud-agent.
> SSVM and CPVM are pingable, but not accessible. CPVM is showing "Connection
> Refused" when attempting to use console. SSVM does not respond to ISO or
> Template upload requests. Both System VMs show "running" in console.
> ssh -i /root/.ssh/id_rsa.cloud -p 3922 root@169.254.3.122
> Permission denied (public key)
> I get this on both CPVM and SSVM. I have deleted the ssh keys and force
> connected the host while respinning system VMs to test whether keys are
> formed properly. Mysql is showing keys properly in the database too.
> I suspect System VMs arent being patched when they boot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
