[
https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Roy reopened CLOUDSTACK-4300:
-------------------------------------
Re-opening the bug as the issue is seen again with KVM host CentOS 6.0 on
upgrade from 2.2.14 to 4.2 .
After upgrade when system vms are restarted, they stay in starting state and
never come up in CS even though we can see them running on the agent side.
virsh # list
Id Name State
----------------------------------
4 r-4-VM running
5 i-2-3-VM running
6 s-5-VM running
7 v-6-VM running
[root@kvm60-band19 ~]# rpm -qa | grep libvirt
libvirt-client-0.8.1-27.el6.x86_64
libvirt-0.8.1-27.el6.x86_64
Attaching logs .
> [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4300
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4300
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, SystemVM, Upgrade
> Affects Versions: 4.2.0
> Environment: Host : KVM [CentOS 6.1]
> MS : CentOS 6.1
> upgrade from 2.2.14 to 4.2
> Reporter: Abhinav Roy
> Assignee: edison su
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: CS-4300.zip
>
>
> Steps :
> ================
> 1. Deploy a CS 2.2.14 advanced zone setup with KVM host.
> 2. do some operations like create vm, snapshots, templates, domain, accounts
> etc
> 3. upgrade to 4.2
> Expected behaviour :
> ===============
> Upgrade should go fine and new system vms should come up
> Observed behaviour :
> ==============
> Upgrade went fine but system vms don't come up, they stay in the starting
> state.
> Attaching management server logs, catalina logs, agent 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
