[jira] [Updated] (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:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-4300: --- Assignee: Abhinav Roy [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] [Updated] (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:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-4300: --- Fix Version/s: (was: 4.2.0) 4.2.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: 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.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] [Updated] (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:all-tabpanel ] Radhika Nair updated CLOUDSTACK-4300: - Summary: [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after upgrade (was: [Doc] [upgrade][2.2.14 to 4.2][KVM] system vms are not coming up after 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: 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] [Updated] (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:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4300: - Component/s: Doc [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: edison su 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] [Updated] (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:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-4300: Attachment: re_CS-4300.zip [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, 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] [Updated] (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:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-4300: --- Assignee: edison su [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] [Updated] (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:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-4300: Attachment: CS-4300.zip Network working fine now. attaching 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 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
