incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trevor Francis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-577) CS4 System VMs not patching
Date Mon, 03 Dec 2012 22:05:59 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509107#comment-13509107
] 

Trevor Francis commented on CLOUDSTACK-577:
-------------------------------------------

resolved by a apt-get install cloud-system-iso and an cloud-agent restart.

This should be part of the cloud-agent installation.
                
> 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

Mime
View raw message