[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13790181#comment-13790181 ] Abhinandan Prateek commented on CLOUDSTACK-4300: Abhinav, Did we decide to document the upgrade for KVM, it seem that is already complete. If it is can you close this ticket. [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: Doc, 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: Abhinav Roy Priority: Blocker Fix For: 4.2.1 Attachments: CS-4300.zip, re_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 was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776143#comment-13776143 ] Radhika Nair commented on CLOUDSTACK-4300: -- Created a doc sub task to document this issue. [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: Doc, 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: Jessica Tomechak Priority: Blocker Fix For: 4.2.0 Attachments: CS-4300.zip, re_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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742867#comment-13742867 ] ASF subversion and git services commented on CLOUDSTACK-4300: - Commit ca678a8742c441e5f39d13a3979070c881f3fbe6 in branch refs/heads/4.2 from [~edison] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ca678a8 ] CLOUDSTACK-4300: possible fix: cputune feature is only available after 0.9.0, so start vm can fail on rhel 6.1 [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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13739287#comment-13739287 ] Abhinav Roy commented on CLOUDSTACK-4300: - re-opening the bug as we need more clarity on the upgrade procedure [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 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738363#comment-13738363 ] Wei Zhou commented on CLOUDSTACK-4300: -- Abhinav , could you attach the 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 Priority: Blocker Fix For: 4.2.0 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738369#comment-13738369 ] Abhinav Roy commented on CLOUDSTACK-4300: - Hi Wei, I am not able to connect to the hosts from home. some problem with Citrix Bangalore network . Not able to attach the logs. Thanks and regards, Abhinav [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 Priority: Blocker Fix For: 4.2.0 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738386#comment-13738386 ] Wei Zhou commented on CLOUDSTACK-4300: -- Abhinav, It is OK. Let's work on it tomorrow. [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 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738435#comment-13738435 ] Abhinav Roy commented on CLOUDSTACK-4300: - Wei, I ran that command but i am not able to login to the systemvm, the state is shown as running but when i try to login to the console though virt-manager, i am not Thanks, Abhinav [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 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738510#comment-13738510 ] Wei Zhou commented on CLOUDSTACK-4300: -- Abhinav , Can you use virt-manager or virsh reboot [vmName] command to reboot the vm? -Wei [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 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738538#comment-13738538 ] edison su commented on CLOUDSTACK-4300: --- Need to upgrade KVM host to at least RHEL 6.3 before upgrade to cloudstack 4.2. [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 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738554#comment-13738554 ] Abhinav Roy commented on CLOUDSTACK-4300: - so, we dont support any lower version KVM for 4.2 ? we need to mandatorily upgrade the KVM host to 6.3 before upgrade ? [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 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
[jira] [Commented] (CLOUDSTACK-4300) [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738644#comment-13738644 ] Animesh Chaturvedi commented on CLOUDSTACK-4300: Abhinav is this is missing documentation can you file a DOC issue [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 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
