cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Artemyev (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-6385) Can`t update systemvm.iso and authorized_keys on host after upgrade from 4.2 to 4.3
Date Wed, 16 Apr 2014 03:19:14 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Artemyev updated CLOUDSTACK-6385:
----------------------------------------

    Description: 
when I upgrade managment the server from 4.2 to 4.3. new ssh key-pair generated and intergate
to systemvm.iso, but neither new publickey no systemvm.iso not upload to hypervisor hosts
as result upgraded systemvm`s started but down by hypervisor which can`t access to it.
clean install of CS not have this problem

  was:
when I upgrade managment the server from 4.2 to 4.3. new ssh key-pair generated and intergate
to systemvm.iso, but neither new publickey no systemvm.iso not upload to hypervisor host
as result upgraded systemvm started but down by hypervisor which can`t access to it.
clean install of CS not have this problem


> Can`t update systemvm.iso and authorized_keys on host after upgrade from 4.2 to 4.3
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6385
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6385
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, SystemVM, XenServer
>    Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.2.0, 4.3.0
>            Reporter: Andrew Artemyev
>
> when I upgrade managment the server from 4.2 to 4.3. new ssh key-pair generated and intergate
to systemvm.iso, but neither new publickey no systemvm.iso not upload to hypervisor hosts
> as result upgraded systemvm`s started but down by hypervisor which can`t access to it.
> clean install of CS not have this problem



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message