cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinav Roy (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-4554) [upgrade from 3.0.6 to 4.2][vmware] System VM agent doesn't come up after adding a zone on an upgraded setup
Date Thu, 29 Aug 2013 20:58:51 GMT

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

Abhinav Roy closed CLOUDSTACK-4554.
-----------------------------------


Closing the issue as it is not observed anymore
                
> [upgrade from 3.0.6 to 4.2][vmware] System VM agent doesn't come up after adding a zone
on an upgraded setup
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4554
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4554
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: SystemVM, Upgrade, VMware
>    Affects Versions: 4.2.0
>         Environment: upgrade from 3.0.6 to 4.2
> host : esx 4.1 and esx 5.0
>            Reporter: Abhinav Roy
>            Priority: Blocker
>             Fix For: 4.2.1
>
>         Attachments: CS-4554.zip
>
>
> Steps :
> ===========================
> 1. Deploy a CS 3.0.6 advanced zone network with esx 4.1 host.
> 2. create VMs, snapshots, templates etc.
> 3. upgrade to CS 4.2
> 4. Add a zone with Esx 5.0
> Expected behaviour :
> ===========================
> System vms for the newly added zone should come up and their agent status should be running.
> Observed behaviour :
> ==========================
> System vms of the newly added zone do come up but their agent status is not up.
> Their entry is not there in cloud.host tables.
> Attaching all relevant logs and db dumps

--
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