[jira] [Created] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
shweta agarwal created CLOUDSTACK-7211: -- Summary: system VM not coming up in LXC zone for rhel 6.x Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Priority: Blocker Fix For: 4.5.0 created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shweta agarwal updated CLOUDSTACK-7211: --- Attachment: agent.tar.gz MS.tar.gz system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7212) Failed to create LB rule on public port 8081
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy updated CLOUDSTACK-7212: -- Component/s: Network Controller Affects Version/s: 4.0.0 Fix Version/s: 4.5.0 Assignee: Jayapal Reddy Failed to create LB rule on public port 8081 Key: CLOUDSTACK-7212 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7212 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Creating to LB rule on public port 8081 is failed on VR as a LB provider. This is because the haproxy in VR is listening on the public ip for LB stats. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7212) Failed to create LB rule on public port 8081
Jayapal Reddy created CLOUDSTACK-7212: - Summary: Failed to create LB rule on public port 8081 Key: CLOUDSTACK-7212 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7212 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jayapal Reddy Creating to LB rule on public port 8081 is failed on VR as a LB provider. This is because the haproxy in VR is listening on the public ip for LB stats. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7213) Cloud-setup-databases script should not fail if no SELinux is installed
Jayapal Reddy created CLOUDSTACK-7213: - Summary: Cloud-setup-databases script should not fail if no SELinux is installed Key: CLOUDSTACK-7213 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7213 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.0.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 We should update ou scripts to check if Selinux is installed, and only if it is installed check if it is set to permissive mode, if it is not installed we should not fail (as far as I can tell we do not have dependancy on SElinux) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-7211: -- Assignee: Amogh Vasekar system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080754#comment-14080754 ] Kishan Kavala commented on CLOUDSTACK-7211: --- Amogh, Can you please add guest OS mapping related changes to LXCGuru.java similar to KVMGuru.java system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at
[jira] [Reopened] (CLOUDSTACK-6358) Remove hardcoded guest OS mappings
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek reopened CLOUDSTACK-6358: CLOUDSTACK-6358 made changes to guestOS mapping across all hypervisors. But LXC related changes are missing, can these be also added as missing LXC hanged cause https://issues.apache.org/jira/browse/CLOUDSTACK-7211. Remove hardcoded guest OS mappings -- Key: CLOUDSTACK-6358 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6358 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Amogh Vasekar Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.4.0, 4.5.0 The guest OS to platform emulator mappings are hardcoded in the codebase. This needs to be removed so as to support dynamic addition of guest OS type -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7214) [LDAP] connection timeout is hardcoded to 500ms
Rajani Karuturi created CLOUDSTACK-7214: --- Summary: [LDAP] connection timeout is hardcoded to 500ms Key: CLOUDSTACK-7214 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7214 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Rajani Karuturi Assignee: Rajani Karuturi Fix For: 4.5.0 if the ldap connection takes more than 500ms to respond, it timeout and doesnt return any users. There is no way to change this value from a configuration. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7214) [LDAP] connection timeout is hardcoded to 500ms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14080786#comment-14080786 ] ASF subversion and git services commented on CLOUDSTACK-7214: - Commit cd2f27a6628472b1c0a6289989dc802f534ec74e in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cd2f27a ] Fixed bug: CLOUDSTACK-7214 added a config for ldap connection read timeout. [LDAP] connection timeout is hardcoded to 500ms --- Key: CLOUDSTACK-7214 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7214 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Rajani Karuturi Assignee: Rajani Karuturi Fix For: 4.5.0 if the ldap connection takes more than 500ms to respond, it timeout and doesnt return any users. There is no way to change this value from a configuration. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7214) [LDAP] connection timeout is hardcoded to 500ms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-7214. - Resolution: Fixed [LDAP] connection timeout is hardcoded to 500ms --- Key: CLOUDSTACK-7214 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7214 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Rajani Karuturi Assignee: Rajani Karuturi Fix For: 4.5.0 if the ldap connection takes more than 500ms to respond, it timeout and doesnt return any users. There is no way to change this value from a configuration. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7216) Cloudstack 4.4 on Xen 6.2 using this system template
Dean Kamali created CLOUDSTACK-7216: --- Summary: Cloudstack 4.4 on Xen 6.2 using this system template Key: CLOUDSTACK-7216 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7216 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: CS 4.4 / XenServer 6.2 Reporter: Dean Kamali Using SSVM template in documentation http://download.cloud.com/templates/4.3/systemvm64template-2014-06-23-master-xen.vhd.bz2 Running SSVM check on secondary storage VM will reval that JAVA process is not running. This will result in inability to setup templates or take snapshots # /usr/local/cloud/systemvm/ssvm-check.sh root@s-29-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 48 data bytes 56 bytes from 8.8.8.8: icmp_seq=0 ttl=49 time=8.900 ms 56 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=8.525 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 8.525/8.713/8.900/0.188 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com nfs is currently mounted Management server is 172.16.0.68. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. root@s-29-VM:~# service cloud status CloudStack cloud service is not running root@s-29-VM:~# service cloud start Starting CloudStack cloud service (type=secstorage) Success root@s-29-VM:~# service cloud status CloudStack cloud service is not running -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7215) [Automation] Make expunge=True as default parameter value for destroyVirtualMachine api call through base library
Gaurav Aradhye created CLOUDSTACK-7215: -- Summary: [Automation] Make expunge=True as default parameter value for destroyVirtualMachine api call through base library Key: CLOUDSTACK-7215 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7215 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Gaurav Aradhye Assignee: Gaurav Aradhye Fix For: 4.5.0 In almost 90% of the scenarios where VMs are created through test case, VMs are added to cleanup list and the delete method is called for them through cleanup_resources method in utils.py file. These VMs remain in destroyed state for long time and keep blocking the resources (IP Address etc) and hence the load on the setup on which regression build is fired increases. Making expunge=True as default parameter in destroyVirtualMachine api call through base library will make all these VMs expunge quickly making resources available for next test cases. Also, it can be passed as False whenever we don't want VM to expunge immediately, and in case when we recover the VM through test case after destroying it. Pass expunge=False for all such scenarios. This will hugely boost the test cases execution speed too. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7216) Cloudstack 4.4 on Xen 6.2 ERROR: Java process not running
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dean Kamali updated CLOUDSTACK-7216: Summary: Cloudstack 4.4 on Xen 6.2 ERROR: Java process not running (was: Cloudstack 4.4 on Xen 6.2 using this system template) Cloudstack 4.4 on Xen 6.2 ERROR: Java process not running - Key: CLOUDSTACK-7216 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7216 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: CS 4.4 / XenServer 6.2 Reporter: Dean Kamali Using SSVM template in documentation http://download.cloud.com/templates/4.3/systemvm64template-2014-06-23-master-xen.vhd.bz2 Running SSVM check on secondary storage VM will reval that JAVA process is not running. This will result in inability to setup templates or take snapshots # /usr/local/cloud/systemvm/ssvm-check.sh root@s-29-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 48 data bytes 56 bytes from 8.8.8.8: icmp_seq=0 ttl=49 time=8.900 ms 56 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=8.525 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 8.525/8.713/8.900/0.188 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com nfs is currently mounted Management server is 172.16.0.68. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. root@s-29-VM:~# service cloud status CloudStack cloud service is not running root@s-29-VM:~# service cloud start Starting CloudStack cloud service (type=secstorage) Success root@s-29-VM:~# service cloud status CloudStack cloud service is not running -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7216) Cloudstack 4.4 on Xen 6.2 ERROR: Java process not running
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dean Kamali updated CLOUDSTACK-7216: Description: Using SSVM template in documentation http://download.cloud.com/templates/4.3/systemvm64template-2014-06-23-master-xen.vhd.bz2 Running SSVM check on secondary storage VM will reveal that JAVA process is not running. This will result in inability to setup templates or take snapshots # /usr/local/cloud/systemvm/ssvm-check.sh root@s-29-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 48 data bytes 56 bytes from 8.8.8.8: icmp_seq=0 ttl=49 time=8.900 ms 56 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=8.525 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 8.525/8.713/8.900/0.188 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com nfs is currently mounted Management server is 172.16.0.68. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. root@s-29-VM:~# service cloud status CloudStack cloud service is not running root@s-29-VM:~# service cloud start Starting CloudStack cloud service (type=secstorage) Success root@s-29-VM:~# service cloud status CloudStack cloud service is not running was: Using SSVM template in documentation http://download.cloud.com/templates/4.3/systemvm64template-2014-06-23-master-xen.vhd.bz2 Running SSVM check on secondary storage VM will reval that JAVA process is not running. This will result in inability to setup templates or take snapshots # /usr/local/cloud/systemvm/ssvm-check.sh root@s-29-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 48 data bytes 56 bytes from 8.8.8.8: icmp_seq=0 ttl=49 time=8.900 ms 56 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=8.525 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 8.525/8.713/8.900/0.188 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com nfs is currently mounted Management server is 172.16.0.68. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. root@s-29-VM:~# service cloud status CloudStack cloud service is not running root@s-29-VM:~# service cloud start Starting CloudStack cloud service (type=secstorage) Success root@s-29-VM:~# service cloud status CloudStack cloud service is not running Cloudstack 4.4 on Xen 6.2 ERROR: Java process not running - Key: CLOUDSTACK-7216 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7216 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: CS 4.4 / XenServer 6.2 Reporter: Dean Kamali Using SSVM template in documentation http://download.cloud.com/templates/4.3/systemvm64template-2014-06-23-master-xen.vhd.bz2 Running SSVM check on secondary storage VM will reveal that JAVA process is not running. This will result in inability to setup templates or take snapshots # /usr/local/cloud/systemvm/ssvm-check.sh root@s-29-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 48 data bytes 56 bytes from 8.8.8.8: icmp_seq=0 ttl=49 time=8.900 ms 56 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=8.525 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 8.525/8.713/8.900/0.188 ms Good: Can ping DNS server Good: DNS resolves download.cloud.com nfs is currently mounted Management server is 172.16.0.68. Checking connectivity. Good: Can connect to management server port 8250 ERROR: Java process not running. Try restarting the SSVM. root@s-29-VM:~# service cloud status CloudStack cloud service is not
[jira] [Commented] (CLOUDSTACK-6931) LXC agent install : hypervisor.type not set
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081102#comment-14081102 ] ASF subversion and git services commented on CLOUDSTACK-6931: - Commit ccee282a743c1814d7c2ff969da98d567b26bf85 in cloudstack's branch refs/heads/4.4 from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ccee282 ] CLOUDSTACK-6931: Set hypervisor.type in agent.properties using cloudstack-setup -t option. Default is kvm. (cherry picked from commit 89854de18da62d0808363781ad27fc310eb9b8cd) Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com LXC agent install : hypervisor.type not set --- Key: CLOUDSTACK-6931 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6931 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.5.0 While adding LXC host, hypervisor.type param in agent.properties is not set. Agent defaults to KVM when the param is not set. cloudstack-agent-setup script should update hypervisor.type as lxc -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081119#comment-14081119 ] ASF subversion and git services commented on CLOUDSTACK-7211: - Commit 89fabe82b9b28df7405022a1707f71dbddfe1604 in cloudstack's branch refs/heads/master from [~bhaisaab] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=89fabe8 ] CLOUDSTACK-7211: Add Guest OS mapping before returning VirtualMachineTO object Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at
[jira] [Commented] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081124#comment-14081124 ] ASF subversion and git services commented on CLOUDSTACK-7211: - Commit d79251853b1c494808e1c9885ddab2b65db5f6d3 in cloudstack's branch refs/heads/4.4 from [~bhaisaab] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d792518 ] CLOUDSTACK-7211: Add Guest OS mapping before returning VirtualMachineTO object Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com (cherry picked from commit 89fabe82b9b28df7405022a1707f71dbddfe1604) Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at
[jira] [Assigned] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav reassigned CLOUDSTACK-7211: --- Assignee: Rohit Yadav (was: Amogh Vasekar) system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Rohit Yadav Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav resolved CLOUDSTACK-7211. - Resolution: Fixed Fixed on 4.4 and master branch system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Rohit Yadav Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081127#comment-14081127 ] Rohit Yadav commented on CLOUDSTACK-7211: - Looks like the 4.4 release was the worst ever release. LXC was practically broken. I've tried to fix it and cherry pick the Kishan's fix of cloud-setup-agent from master (ccee282a743c1814d7c2ff969da98d567b26bf85) Please test and close it. Reopen in case of error and we'll have Amogh take a second look. system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at
[jira] [Commented] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081139#comment-14081139 ] Amogh Vasekar commented on CLOUDSTACK-7211: --- Hi, I am assuming the hypervisor_type for LXC host is recorded as LXC. Is that correct? If yes, we would need to add the mappings to the guest_os_hypervisor table as well. If it was sharing the mappings from KVMGuestOsMapper, we can copy all the KVM related mappings in the DB. Thanks! system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Rohit Yadav Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at
[jira] [Updated] (CLOUDSTACK-7078) CLONE - [VMWARE]System VM's are failed to start with Nexus enabled Zone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi updated CLOUDSTACK-7078:
-
Fix Version/s: (was: 4.4.0)
CLONE - [VMWARE]System VM's are failed to start with Nexus enabled Zone
Key: CLOUDSTACK-7078
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7078
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Devices, VMware
Affects Versions: 4.4.0
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Priority: Critical
Fix For: 4.5.0
Attachments: issuenexus.rar
Steps:
1. Upgraded from 3.0.7 to 4.2 ( VMWARE Zone with Standard vSwitch)
2. Enable Nexus global config variable
3. Tried to add new Zone with VMWARE Nexus enabled
4. Added two physical networks ( 1 - Mgmt - vSwitch0,,vmwaresvs 2- Public
guest - sailajanewpp,,nexusdvs)
5. Provided VSM details while adding cluster
Observation:
System VM's are failed to start with Nexus enabled Zone saying Nexus details
can not be retrieved from DB.
2013-08-22 00:37:01,732 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===START=== 10.101.255.30 -- GET
command=queryAsyncJobResultjobId=921f4c19-a655-4234-82c4-66efcbe73933response=jsonsessionkey=CNY1grUrySJwTE%2BpFM3btn1i4Xs%3D_=1377112271133
2013-08-22 00:37:01,782 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.101.255.30 -- GET
command=queryAsyncJobResultjobId=921f4c19-a655-4234-82c4-66efcbe73933response=jsonsessionkey=CNY1grUrySJwTE%2BpFM3btn1i4Xs%3D_=1377112271133
2013-08-22 00:37:02,170 WARN [vmware.resource.VmwareResource]
(DirectAgent-128:10.102.192.18) StartCommand failed due to Exception:
java.lang.Exception
Message: Failed to retrieve required credentials of Nexus VSM from database.
java.lang.Exception: Failed to retrieve required credentials of Nexus VSM
from database.
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.getValidatedVsmCredentials(HypervisorHostHelper.java:183)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.createPortProfile(HypervisorHostHelper.java:201)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:584)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3308)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2904)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-08-22 00:37:02,196 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-128:null) Seq 14-773455885: Cancelling because one of the
answers is false and it is stop on error.
2013-08-22 00:37:02,196 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-128:null) Seq 14-773455885: Response Received:
2013-08-22 00:37:02,199 DEBUG [agent.transport.Request]
(DirectAgent-128:null) Seq 14-773455885: Processing: { Ans: , MgmtId:
187767034175903, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.StartAnswer:{vm:{id:30,name:s-30-VM,bootloader:HVM,type:SecondaryStorageVm,cpus:1,minSpeed:500,maxSpeed:500,minRam:268435456,maxRam:268435456,hostName:s-30-VM,arch:x86_64,os:Debian
GNU/Linux 5.0 (32-bit),bootArgs: template=domP type=secstorage
host=10.102.192.207 port=8250 name=s-30-VM zone=3 pod=3 guid=s-30-VM
resource=com.cloud.storage.resource.PremiumSecondaryStorageResource
instance=SecStorage sslcopy=true role=templateProcessor mtu=1500
eth2ip=10.102.196.220 eth2mask=255.255.255.0 gateway=10.102.196.1
public.network.device=eth2 eth0mask=0.0.0.0 eth0ip=0.0.0.0
eth1ip=10.102.195.150 eth1mask=255.255.252.0 mgmtcidr=10.102.192.0/22
localgw=10.102.192.1 private.network.device=eth1 eth3ip=10.102.195.152
eth3mask=255.255.252.0
[jira] [Reopened] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav reopened CLOUDSTACK-7211: - system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-7211) system VM not coming up in LXC zone for rhel 6.x
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav reassigned CLOUDSTACK-7211: --- Assignee: Amogh Vasekar (was: Rohit Yadav) Alright, please go ahead and fix it on 4.4 and master. Thanks. system VM not coming up in LXC zone for rhel 6.x -- Key: CLOUDSTACK-7211 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7211 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Amogh Vasekar Priority: Blocker Fix For: 4.5.0 Attachments: MS.tar.gz, agent.tar.gz created a zone with LXC hypervisor on rhel 6.3 host Pre seeded the KVM template as LXC On enabling zone Syemt VMs are not coming up Agent log shows : ttempting to create storage pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,260 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create storage pool 4032a858-88b0-3c03-8477-8984eb6b390b (NetworkFilesystem) in libvirt 2014-07-31 04:56:50,417 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to create volume 1c123c1a-1873-11e4-87de-4524e40b898e (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,052 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-1:null) Attempting to remove storage pool 4032a858-88b0-3c03-8477-8984eb6b390b from libvirt 2014-07-31 04:57:14,388 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Creating volume 75d88b46-1b93-4065-a348-460b8d3911fb from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:14,389 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-2:null) Attempting to create volume 75d88b46-1b93-4065-a348-460b8d3911fb (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:14,948 WARN [cloud.agent.Agent] (agentRequest-Handler-3:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 2014-07-31 04:57:15,700 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Creating volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 from template 1c123c1a-1873-11e4-87de-4524e40b898e in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 (NetworkFilesystem) with size 0 2014-07-31 04:57:15,701 INFO [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-5:null) Attempting to create volume cac2c108-9f11-4ad7-981e-92a4a0bd05d4 (NetworkFilesystem) in pool dfa2ec3c-d133-3284-8583-0a0845aa4424 with size 262144 2014-07-31 04:57:16,262 WARN [cloud.agent.Agent] (agentRequest-Handler-1:null) Caught: java.lang.NullPointerException at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:3990) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3733) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1332) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) -- This message
[jira] [Commented] (CLOUDSTACK-7078) CLONE - [VMWARE]System VM's are failed to start with Nexus enabled Zone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081216#comment-14081216
]
ASF subversion and git services commented on CLOUDSTACK-7078:
-
Commit 96a6e673a3dcfcb6c27bd56264e388ccd68f9e47 in cloudstack's branch
refs/heads/master from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=96a6e67 ]
CLOUDSTACK-7078 CLONE - [VMWARE]System VM's are failed to start with Nexus
enabled Zone Since introducing pool of session contexts we no more have a
dedicated context for each VMware hypervisor host. Hence vsm credentials stored
in session context cannot be retrieved always correctly. Fix is to register the
vsm credentials after fetching context and the context gets recycled after use.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
CLONE - [VMWARE]System VM's are failed to start with Nexus enabled Zone
Key: CLOUDSTACK-7078
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7078
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Devices, VMware
Affects Versions: 4.4.0
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Priority: Critical
Fix For: 4.5.0
Attachments: issuenexus.rar
Steps:
1. Upgraded from 3.0.7 to 4.2 ( VMWARE Zone with Standard vSwitch)
2. Enable Nexus global config variable
3. Tried to add new Zone with VMWARE Nexus enabled
4. Added two physical networks ( 1 - Mgmt - vSwitch0,,vmwaresvs 2- Public
guest - sailajanewpp,,nexusdvs)
5. Provided VSM details while adding cluster
Observation:
System VM's are failed to start with Nexus enabled Zone saying Nexus details
can not be retrieved from DB.
2013-08-22 00:37:01,732 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===START=== 10.101.255.30 -- GET
command=queryAsyncJobResultjobId=921f4c19-a655-4234-82c4-66efcbe73933response=jsonsessionkey=CNY1grUrySJwTE%2BpFM3btn1i4Xs%3D_=1377112271133
2013-08-22 00:37:01,782 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.101.255.30 -- GET
command=queryAsyncJobResultjobId=921f4c19-a655-4234-82c4-66efcbe73933response=jsonsessionkey=CNY1grUrySJwTE%2BpFM3btn1i4Xs%3D_=1377112271133
2013-08-22 00:37:02,170 WARN [vmware.resource.VmwareResource]
(DirectAgent-128:10.102.192.18) StartCommand failed due to Exception:
java.lang.Exception
Message: Failed to retrieve required credentials of Nexus VSM from database.
java.lang.Exception: Failed to retrieve required credentials of Nexus VSM
from database.
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.getValidatedVsmCredentials(HypervisorHostHelper.java:183)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.createPortProfile(HypervisorHostHelper.java:201)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:584)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3308)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2904)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-08-22 00:37:02,196 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-128:null) Seq 14-773455885: Cancelling because one of the
answers is false and it is stop on error.
2013-08-22 00:37:02,196 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-128:null) Seq 14-773455885: Response Received:
2013-08-22 00:37:02,199 DEBUG [agent.transport.Request]
(DirectAgent-128:null) Seq 14-773455885: Processing: { Ans: , MgmtId:
187767034175903, via: 14, Ver: v1, Flags: 10,
[jira] [Resolved] (CLOUDSTACK-7078) CLONE - [VMWARE]System VM's are failed to start with Nexus enabled Zone
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sateesh Chodapuneedi resolved CLOUDSTACK-7078.
--
Resolution: Fixed
CLONE - [VMWARE]System VM's are failed to start with Nexus enabled Zone
Key: CLOUDSTACK-7078
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7078
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Devices, VMware
Affects Versions: 4.4.0
Reporter: Sateesh Chodapuneedi
Assignee: Sateesh Chodapuneedi
Priority: Critical
Fix For: 4.5.0
Attachments: issuenexus.rar
Steps:
1. Upgraded from 3.0.7 to 4.2 ( VMWARE Zone with Standard vSwitch)
2. Enable Nexus global config variable
3. Tried to add new Zone with VMWARE Nexus enabled
4. Added two physical networks ( 1 - Mgmt - vSwitch0,,vmwaresvs 2- Public
guest - sailajanewpp,,nexusdvs)
5. Provided VSM details while adding cluster
Observation:
System VM's are failed to start with Nexus enabled Zone saying Nexus details
can not be retrieved from DB.
2013-08-22 00:37:01,732 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===START=== 10.101.255.30 -- GET
command=queryAsyncJobResultjobId=921f4c19-a655-4234-82c4-66efcbe73933response=jsonsessionkey=CNY1grUrySJwTE%2BpFM3btn1i4Xs%3D_=1377112271133
2013-08-22 00:37:01,782 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.101.255.30 -- GET
command=queryAsyncJobResultjobId=921f4c19-a655-4234-82c4-66efcbe73933response=jsonsessionkey=CNY1grUrySJwTE%2BpFM3btn1i4Xs%3D_=1377112271133
2013-08-22 00:37:02,170 WARN [vmware.resource.VmwareResource]
(DirectAgent-128:10.102.192.18) StartCommand failed due to Exception:
java.lang.Exception
Message: Failed to retrieve required credentials of Nexus VSM from database.
java.lang.Exception: Failed to retrieve required credentials of Nexus VSM
from database.
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.getValidatedVsmCredentials(HypervisorHostHelper.java:183)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.createPortProfile(HypervisorHostHelper.java:201)
at
com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:584)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3308)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2904)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:514)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-08-22 00:37:02,196 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-128:null) Seq 14-773455885: Cancelling because one of the
answers is false and it is stop on error.
2013-08-22 00:37:02,196 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-128:null) Seq 14-773455885: Response Received:
2013-08-22 00:37:02,199 DEBUG [agent.transport.Request]
(DirectAgent-128:null) Seq 14-773455885: Processing: { Ans: , MgmtId:
187767034175903, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.StartAnswer:{vm:{id:30,name:s-30-VM,bootloader:HVM,type:SecondaryStorageVm,cpus:1,minSpeed:500,maxSpeed:500,minRam:268435456,maxRam:268435456,hostName:s-30-VM,arch:x86_64,os:Debian
GNU/Linux 5.0 (32-bit),bootArgs: template=domP type=secstorage
host=10.102.192.207 port=8250 name=s-30-VM zone=3 pod=3 guid=s-30-VM
resource=com.cloud.storage.resource.PremiumSecondaryStorageResource
instance=SecStorage sslcopy=true role=templateProcessor mtu=1500
eth2ip=10.102.196.220 eth2mask=255.255.255.0 gateway=10.102.196.1
public.network.device=eth2 eth0mask=0.0.0.0 eth0ip=0.0.0.0
eth1ip=10.102.195.150 eth1mask=255.255.252.0 mgmtcidr=10.102.192.0/22
localgw=10.102.192.1 private.network.device=eth1 eth3ip=10.102.195.152
eth3mask=255.255.252.0 storageip=10.102.195.152
[jira] [Created] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
Prieur Leary created CLOUDSTACK-7217:
Summary: Cannot launch VM after 4.4 Upgrade on KVM
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer that
is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done executing
com.cloud.vm.VmWorkStart for job-31053
2014-07-31 15:43:21,586 WARN [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-a3cfb728) Exception while trying to start secondary storage vm
java.lang.RuntimeException: Job failed due to exception Resource
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081361#comment-14081361
]
Erik Weber commented on CLOUDSTACK-7217:
Is the ssvm actually running? e.g. can you ssh to it's link local ip?
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG
[jira] [Comment Edited] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081361#comment-14081361
]
Erik Weber edited comment on CLOUDSTACK-7217 at 7/31/14 8:03 PM:
-
Is the ssvm actually running? e.g. can you ssh to it's link local ip?
If it is, paste any output that might seem relevant from
/var/log/cloud/cloud.out
was (Author: webern):
Is the ssvm actually running? e.g. can you ssh to it's link local ip?
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081368#comment-14081368
]
Prieur Leary commented on CLOUDSTACK-7217:
--
Negative Erik. Neither Console or Storage SSVM's are running. Other info:
1. An error was made in the upgrade process (my fault); I missed the step of
upgrading the SystemVM Template.
2. We realize no new VM's could start, and upgraded the SystemVM template to
4.4; following the procedure in the CS Wiki.
3. Upon recreating the SSVM's, they will not start, nor will any other VM.
4. All of the hosts and agents show up, and we have verified connectivity
between management server and the hosts (ICMP, SSH, Agent Log).
Please let me know if there is anything else that can be helpful.
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081411#comment-14081411
]
Erik Weber commented on CLOUDSTACK-7217:
Can you confirm that you added this template:
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2
?
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081419#comment-14081419
]
Prieur Leary commented on CLOUDSTACK-7217:
--
I added this template:
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-kvm.qcow2.bz2
I used the instructions from:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.2+%28KVM%29+System+Vm+Upgrade
However, they were somewhat dated with a table name. If you have another doc,
which provides guidance, I can do it again.
Also, just found an important clue in agent.log from the host that it was
trying to create an agent on (below). I also included libvirt version. We have
many unhappy folks now, so any help you can give is great.
2014-07-31 14:01:53,209 WARN [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-5:null) Unsupported command
2014-07-31 14:32:04,078 WARN [cloud.agent.Agent] (agentRequest-Handler-2:null)
Caught:
java.lang.NullPointerException
at
com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:159)
at
com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:213)
at
com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3215)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1279)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2014-07-31 16:18:57,790 WARN [cloud.agent.Agent] (agentRequest-Handler-4:null)
Caught:
Name: libvirt
Arch: x86_64
Version : 0.10.2
Release : 29.el6_5.9
Size: 5.6 M
Repo: installed
From repo : updates
Summary : Library providing a simple virtualization API
URL : http://libvirt.org/
License : LGPLv2+
Description : Libvirt is a C toolkit to interact with the virtualization
capabilities
: of recent versions of Linux (and other OSes). The main package
includes
: the libvirtd server exporting the virtualization support.
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081431#comment-14081431
]
Erik Weber commented on CLOUDSTACK-7217:
Could you add some more previous lines from the agent.log?
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081440#comment-14081440 ] Prieur Leary commented on CLOUDSTACK-7217: -- 2014-07-31 14:01:36,272 INFO [utils.nio.NioClient] (Agent-Selector:null) Connecting to 10.30.0.2:8250 2014-07-31 14:01:36,597 INFO [utils.nio.NioClient] (Agent-Selector:null) SSL: Handshake done 2014-07-31 14:01:36,597 INFO [utils.nio.NioClient] (Agent-Selector:null) Connected to 10.30.0.2:8250 2014-07-31 14:01:37,262 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Proccess agent startup answer, agent id = 0 2014-07-31 14:01:37,263 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Set agent id 0 2014-07-31 14:01:37,263 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Startup Response Received: agent id = 0 2014-07-31 14:01:41,598 INFO [cloud.agent.Agent] (Agent-Handler-3:null) Connected to the server 2014-07-31 14:01:46,746 INFO [cloud.agent.Agent] (agentRequest-Handler-4:null) Proccess agent ready command, agent id = 14 2014-07-31 14:01:46,746 INFO [cloud.agent.Agent] (agentRequest-Handler-4:null) Set agent id 14 2014-07-31 14:01:46,747 INFO [cloud.agent.Agent] (agentRequest-Handler-4:null) Ready command is processed: agent id = 14 2014-07-31 14:01:46,893 INFO [cloud.agent.Agent] (agentRequest-Handler-2:null) Proccess agent ready command, agent id = 14 2014-07-31 14:01:46,893 INFO [cloud.agent.Agent] (agentRequest-Handler-2:null) Set agent id 14 2014-07-31 14:01:46,894 INFO [cloud.agent.Agent] (agentRequest-Handler-2:null) Ready command is processed: agent id = 14 2014-07-31 14:01:53,209 WARN [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-5:null) Unsupported command 2014-07-31 14:32:04,078 WARN [cloud.agent.Agent] (agentRequest-Handler-2:null) Caught: java.lang.NullPointerException at com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:159) at com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:213) at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3215) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1279) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) 2014-07-31 16:18:57,790 WARN [cloud.agent.Agent] (agentRequest-Handler-4:null) Caught: java.lang.NullPointerException at com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:159) at com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:213) at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3215) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1279) Cannot launch VM after 4.4 Upgrade on KVM - Key: CLOUDSTACK-7217 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Affects Versions: 4.4.0 Environment: CentOS 6 Reporter: Prieur Leary Priority: Critical Cannot launch VM after 4.4 upgrade. Management server logs following: 2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release cpu from host: 15, old used: 25500,reserved: 0, actual total$ 2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl] (Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release mem from host: 15, old used: 37044092928,reserved: 0, total:$ 2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Invocation exception, caused by: com.cloud.exception.AgentUnavaila$ 2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow exception com.cloud.exception.AgentUnavailableException: R$ 2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-157:ctx-089a5f26
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081445#comment-14081445
]
Prieur Leary commented on CLOUDSTACK-7217:
--
More clues from cloudstack-agent.err. Looks like it is trying to access VM
Instances (domains) that are non-existent.
libvir: LXC Driver error : Domain not found: No domain with matching name
'i-125-1567-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'i-189-1828-VM'
libvir: LXC Driver error : Domain not found: No domain with matching name
'i-189-1828-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
libvir: LXC Driver error : Domain not found: No domain with matching name
'v-3565-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
libvir: LXC Driver error : Domain not found: No domain with matching name
'v-3565-VM'
libvir: QEMU Driver error : Domain not found: no domain with matching name
'v-3565-VM'
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081477#comment-14081477
]
Erik Weber commented on CLOUDSTACK-7217:
could you issue this command on the kvm host to change to debug output and
restart cloudstack-agent?
sed -i 's/INFO/DEBUG/g' /etc/cloudstack/agent/log4j-cloud.xml
also paste a new relevant log output from a start attempt.
I'm pretty sure i'm seeing the same, but are trying to find a workaround / fix
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081491#comment-14081491
]
Prieur Leary commented on CLOUDSTACK-7217:
--
Done. Just waiting for a start attempt.
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081521#comment-14081521
]
Prieur Leary commented on CLOUDSTACK-7217:
--
This is when the last VM tried to start.
2014-07-31 17:30:56,908 DEBUG [cloud.agent.Agent] (agentRequest-Handler-2:null)
Processing command: com.cloud.agent.api.StartCommand
2014-07-31 17:31:02,734 DEBUG [kvm.storage.KVMStoragePoolManager]
(agentRequest-Handler-2:null) Disconnecting disk
0f05b5b1-43da-42ff-92af-922bbf7d4554
2014-07-31 17:31:06,380 DEBUG [cloud.agent.Agent] (agentRequest-Handler-2:null)
Seq 14-4996743786567565373: { Ans: , MgmtId: 152663704217, via: 14, Ver: v1,
Flags: 10, [{com.cloud.agent.api.Answ$
2014-07-31 17:31:06,665 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null)
Request:Seq 14-4996743786567565374: { Cmd , MgmtId: 152663704217, via: 14,
Ver: v1, Flags: 100011, [{com.cloud.age$
2014-07-31 17:31:06,665 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null)
Processing command: com.cloud.agent.api.StopCommand
2014-07-31 17:31:06,668 DEBUG [kvm.resource.LibvirtConnection]
(agentRequest-Handler-1:null) can't find connection: KVM, for vm: s-3893-VM,
continue
2014-07-31 17:31:06,670 DEBUG [kvm.resource.LibvirtConnection]
(agentRequest-Handler-1:null) can't find connection: LXC, for vm: s-3893-VM,
continue
2014-07-31 17:31:06,670 DEBUG [kvm.resource.LibvirtConnection]
(agentRequest-Handler-1:null) can't find which hypervisor the vm used , then
use the default hypervisor
2014-07-31 17:31:06,672 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Failed to get dom xml:
org.libvirt.LibvirtException: Domain not found: no domain with matching n$
2014-07-31 17:31:06,674 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Failed to get dom xml:
org.libvirt.LibvirtException: Domain not found: no domain with matching n$
2014-07-31 17:31:06,676 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Failed to get dom xml:
org.libvirt.LibvirtException: Domain not found: no domain with matching n$
2014-07-31 17:31:06,676 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Executing:
/usr/share/cloudstack-common/scripts/vm/network/security_group.py
destroy_network_rul$
2014-07-31 17:31:06,858 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Execution is successful.
2014-07-31 17:31:06,859 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Try to stop the vm at first
2014-07-31 17:31:06,861 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) VM s-3893-VM doesn't exist, no need to stop it
2014-07-31 17:31:06,862 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null)
Seq 14-4996743786567565374: { Ans: , MgmtId: 152663704217, via: 14, Ver: v1,
Flags: 10, [{com.cloud.agent.api.Stop$
2014-07-31 17:31:11,401 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null)
Processing command: com.cloud.agent.api.GetHostStatsCommand
2014-07-31 17:31:11,402 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing: /bin/bash -c idle=$(top -b -n 1|grep
Cpu\(s\):|cut -d% -f4|cut -d, -f2);echo $idle
2014-07-31 17:31:11,939 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2014-07-31 17:31:11,939 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing: /bin/bash -c freeMem=$(free|grep
cache:|awk '{print $4}');echo $freeMem
2014-07-31 17:31:11,945 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2014-07-31 17:31:11,945 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing: /bin/bash -c free|grep Mem:|awk
'{print $2}'
2014-07-31 17:31:11,950 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2014-07-31 17:31:27,051 DEBUG [kvm.resource.KVMHAMonitor] (Thread-20:null)
Found NFS storage pool d7e65e0e-9d21-3a24-ba56-45973c31dde7 in libvirt,
continuing
2014-07-31 17:31:27,051 DEBUG [kvm.resource.KVMHAMonitor] (Thread-20:null)
Executing:
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh -i
10.30.0.155 -p /mnt/Primary201/Prima$
2014-07-31 17:31:27,068 DEBUG [kvm.resource.KVMHAMonitor] (Thread-20:null)
Execution is successful.
2014-07-31 17:31:27,072 DEBUG [kvm.resource.KVMHAMonitor] (Thread-20:null)
Found NFS storage pool cdad7fd2-36fe-37f3-bba2-04acb043ea78 in libvirt,
continuing
2014-07-31 17:31:27,072 DEBUG [kvm.resource.KVMHAMonitor] (Thread-20:null)
Executing:
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh -i
10.30.0.5 -p /mnt/CS1/Primary -m /mn$
2014-07-31 17:31:27,086 DEBUG [kvm.resource.KVMHAMonitor] (Thread-20:null)
Execution is successful.
2014-07-31
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081530#comment-14081530
]
Erik Weber commented on CLOUDSTACK-7217:
I believe this to be the same as
https://issues.apache.org/jira/browse/CLOUDSTACK-6893, but to verify, could you
grep for No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none in
/var/log/cloudstack/agent/cloudstack-agent.out?
grep No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none
/var/log/cloudstack/agent/cloudstack-agent.out
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081538#comment-14081538
]
Prieur Leary commented on CLOUDSTACK-7217:
--
er:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:29:42,879{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-5:) Seq 14-4996743786567565367: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:30:04,160{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-1:) Seq 14-4996743786567565369: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:31:06,380{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-2:) Seq 14-4996743786567565373: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:34:08,647{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-5:) Seq 14-4996743786567565382: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:34:38,630{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:) Seq 14-4996743786567565385: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:35:08,978{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-2:) Seq 14-4996743786567565388: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:35:39,646{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:) Seq 14-4996743786567565391: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:35:44,838{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-5:) Seq 14-4996743786567565392: { Ans: , MgmtId:
152663704217, via: 14, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:No enum constant
com.cloud.hypervisor.kvm.resource.LibvirtVMDef.DiskDef.diskCacheMode.none,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous
failure,wait:0}},{com.cloud.agent.api.Answer:{result:false,details:Stopped
by previous failure,wait:0}}] }
2014-07-31 17:40:54,189{GMT} DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:) Seq 14-4996743786567565420: { Ans: ,
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081550#comment-14081550
]
Erik Weber commented on CLOUDSTACK-7217:
After that you might want to read
https://gist.github.com/terbolous/102ae8edd1cda192561c
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081549#comment-14081549
]
Prieur Leary commented on CLOUDSTACK-7217:
--
Looks the same?
If so, what is the work around here? Go back to 4.3 Agent?
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081547#comment-14081547
]
Erik Weber commented on CLOUDSTACK-7217:
I don't know of any workaround in 4.4.0 (but I haven't investigated for more
than a few hours).
Someone else might have one that doesn't require new packages, so it's up to
you if you want to wait or try this procedure.
I have verified that it fixes this particular problem in my case, but cannot
guarantee anything
If you are not using any Non-OSS parts of ACS you can try to manually upgrade
your compute host with these packages:
https://www.dropbox.com/sh/x3zjvwy5ca1gpcu/AADsyYTYNQ6WOPoDvKbbnot2a
that is the 4.4.0 + the patch from CLOUDSTACK-6893, but built without
noredist/non-oss modules. If you're using pure kvm + nfs/iscsi you should be
safe.
download anywhere on the host and: rpm -Uvh cloudstack*.rpm
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by:
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081552#comment-14081552
]
Prieur Leary commented on CLOUDSTACK-7217:
--
Got it. Thanks!
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081553#comment-14081553
]
Erik Weber commented on CLOUDSTACK-7217:
You could try downgrading to 4.3 as well, I have no idea how that would go
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG
[jira] [Assigned] (CLOUDSTACK-7210) [Automation] VM Operations failed due to CloudRuntimeException/DB Exception
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-7210: - Assignee: Alena Prokharchyk [Automation] VM Operations failed due to CloudRuntimeException/DB Exception --- Key: CLOUDSTACK-7210 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7210 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: CI Reporter: Raja Pullela Assignee: Alena Prokharchyk Priority: Critical Following SQL exception was seen in the mgmt server log. 02:27:49,102 DEBUG [c.c.u.d.T.Transaction] (Vm-Operations-Cleanup-1:ctx-237bef21) Rolling back the transaction: Time = 19 Name = Vm-Operations-Cleanup-1; called by -TransactionLegacy.rollback:902-TransactionLegacy.removeUpTo:845-TransactionLegacy.close:669-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:204-$Proxy184.expungeCompletedWorkJobs:-1-VirtualMachineManagerImpl$CleanupTask.runInContext:2389-ManagedContextRunnable$1.run:49-DefaultManagedContext$1.call:56 2014-07-28 02:27:49,105 ERROR [c.c.v.VirtualMachineManagerImpl] (Vm-Operations-Cleanup-1:ctx-237bef21) VM Operations failed due to com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@31c304ae: DELETE FROM async_job WHERE async_job.id= 318 at com.cloud.utils.db.GenericDaoBase.expunge(GenericDaoBase.java:1178) at org.apache.cloudstack.framework.jobs.dao.VmWorkJobDaoImpl.expungeCompletedWorkJobs(VmWorkJobDaoImpl.java:149) at sun.reflect.GeneratedMethodAccessor555.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy184.expungeCompletedWorkJobs(Unknown Source) at com.cloud.vm.VirtualMachineManagerImpl$CleanupTask.runInContext(VirtualMachineManagerImpl.java:2389) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`cloud`.`async_job_join_map`, CONSTRAINT `fk_async_job_join_map__join_job_id` FOREIGN KEY (`join_job_id`) REFERENCES `async_job` (`id`)) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
[jira] [Assigned] (CLOUDSTACK-7209) [Automation] NPE observed in the CI Simulator Run on master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk reassigned CLOUDSTACK-7209: - Assignee: Alena Prokharchyk [Automation] NPE observed in the CI Simulator Run on master --- Key: CLOUDSTACK-7209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: CI Reporter: Raja Pullela Assignee: Alena Prokharchyk Priority: Blocker Following NPE is observed on the CI Env: 02:17:16,156 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-72:ctx-6d23d8df job-215/job-216 ctx-cb3c4a4d) Lock is released for network Ntwk[222|Guest|11] as a part of network shutdown 2014-07-28 02:17:16,156 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-72:ctx-6d23d8df job-215/job-216 ctx-cb3c4a4d) Lock is released for network id 222 as a part of network implement 2014-07-28 02:17:16,158 WARN [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] (Work-Job-Executor-72:ctx-6d23d8df job-215/job-216 ctx-cb3c4a4d) Failed to add router VM[DomainRouter|r-38-VM] to network Ntwk[222|Guest|11] due to java.lang.NullPointerException at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createNicForVm(NetworkOrchestrator.java:3077) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:3409) at com.cloud.vm.VirtualMachineManagerImpl.addVmToNetwork(VirtualMachineManagerImpl.java:3355) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.addVpcRouterToGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:267) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy191.addVpcRouterToGuestNetwork(Unknown Source) at com.cloud.network.element.VpcVirtualRouterElement.implement(VpcVirtualRouterElement.java:187) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1088) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:995) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1282) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:985) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5146) at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5302) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081606#comment-14081606
]
Prieur Leary commented on CLOUDSTACK-7217:
--
The fixed worked, and now the SSVM have successfully launched. However, we
cannot launch new VM instances.
We are getting the error below, which seems to put the whole Data Center into
the Avoid Set.
2014-07-31 18:25:55,786 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-16:ctx-c4552da9 job-32156/job-32159 ctx-e0940602) Seq
16-2295709910052111977: Received: { Ans: , MgmtId: 152663704217, via: 16, $
2014-07-31 18:25:55,786 INFO [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Executor-16:ctx-c4552da9 job-32156/job-32159 ctx-e0940602) Unable to
contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is
unreachable: Unable to apply dhcp entry on router
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:4018)
at
com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyDhcpEntry(VirtualNetworkApplianceManagerImpl.java:3134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy188.applyDhcpEntry(Unknown Source)
at
com.cloud.network.element.VirtualRouterElement.addDhcpEntry(VirtualRouterElement.java:905)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareElement(NetworkOrchestrator.java:1221)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1343)
at
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1279)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:985)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081613#comment-14081613
]
Erik Weber commented on CLOUDSTACK-7217:
I think there was an error building it as noredist, to verify could you check
the /var/log/cloud/cloud.out on the ssvm and see if you see a Unable to start
agent: Resource class not found:
com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
java.lang.ClassNotFoundException:
com.cloud.storage.resource.PremiumSecondaryStorageResource error?
If so I'm working on building a fix, but it takes a little time. will repost
when done
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19
[jira] [Created] (CLOUDSTACK-7218) [Automation] NPE observed while deleting account in automation run
Rayees Namathponnan created CLOUDSTACK-7218: --- Summary: [Automation] NPE observed while deleting account in automation run Key: CLOUDSTACK-7218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7218 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: KVM (RHEL 6.3) Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.5.0 This issue is observed in automation log, NPE thrown while deleting account 2014-07-31 02:20:56,102 DEBUG [c.c.n.r.RulesManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) There are no static nat rules to apply for ip id=28 2014-07-31 02:20:56,105 WARN [c.c.u.AccountManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) Failed to cleanup accou nt Acct[b1cf2381-ab36-4ebc-90ff-f08acaf5e02d-test-account-TestVmNetworkOperations-test_add_static_nat_rule_1_ISOLATED-YI0OCS] due to java.lang.NullPointerException at com.cloud.network.rules.RulesManagerImpl.createStaticNatForIp(RulesManagerImpl.java:1391) at com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1321) at com.cloud.network.rules.RulesManagerImpl.revokeAllPFAndStaticNatRulesForIp(RulesManagerImpl.java:1104) at sun.reflect.GeneratedMethodAccessor524.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy105.revokeAllPFAndStaticNatRulesForIp(Unknown Source) at com.cloud.network.IpAddressManagerImpl.cleanupIpResources(IpAddressManagerImpl.java:540) at com.cloud.network.IpAddressManagerImpl.applyIpAssociations(IpAddressManagerImpl.java:936) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.cleanupNetworkResources(NetworkOrchestrator.java:2650) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2196) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:667) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1441) at sun.reflect.GeneratedMethodAccessor542.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy102.deleteUserAccount(Unknown Source) at org.apache.cloudstack.region.RegionManagerImpl.deleteUserAccount(RegionManagerImpl.java:187) at org.apache.cloudstack.region.RegionServiceImpl.deleteUserAccount(RegionServiceImpl.java:121) at org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd.execute(DeleteAccountCmd.java:104)
[jira] [Commented] (CLOUDSTACK-7218) [Automation] NPE observed while deleting account in automation run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081620#comment-14081620 ] Rayees Namathponnan commented on CLOUDSTACK-7218: - Logs are available at https://citrix.sharefile.com/d/sa65c4051903448ab [Automation] NPE observed while deleting account in automation run -- Key: CLOUDSTACK-7218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7218 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: KVM (RHEL 6.3) Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.5.0 This issue is observed in automation log, NPE thrown while deleting account 2014-07-31 02:20:56,102 DEBUG [c.c.n.r.RulesManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) There are no static nat rules to apply for ip id=28 2014-07-31 02:20:56,105 WARN [c.c.u.AccountManagerImpl] (API-Job-Executor-2:ctx-523291d6 job-5302 ctx-28b51397) Failed to cleanup accou nt Acct[b1cf2381-ab36-4ebc-90ff-f08acaf5e02d-test-account-TestVmNetworkOperations-test_add_static_nat_rule_1_ISOLATED-YI0OCS] due to java.lang.NullPointerException at com.cloud.network.rules.RulesManagerImpl.createStaticNatForIp(RulesManagerImpl.java:1391) at com.cloud.network.rules.RulesManagerImpl.applyStaticNatForIp(RulesManagerImpl.java:1321) at com.cloud.network.rules.RulesManagerImpl.revokeAllPFAndStaticNatRulesForIp(RulesManagerImpl.java:1104) at sun.reflect.GeneratedMethodAccessor524.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy105.revokeAllPFAndStaticNatRulesForIp(Unknown Source) at com.cloud.network.IpAddressManagerImpl.cleanupIpResources(IpAddressManagerImpl.java:540) at com.cloud.network.IpAddressManagerImpl.applyIpAssociations(IpAddressManagerImpl.java:936) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.cleanupNetworkResources(NetworkOrchestrator.java:2650) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.destroyNetwork(NetworkOrchestrator.java:2196) at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:793) at com.cloud.user.AccountManagerImpl.deleteAccount(AccountManagerImpl.java:667) at com.cloud.user.AccountManagerImpl.deleteUserAccount(AccountManagerImpl.java:1441) at sun.reflect.GeneratedMethodAccessor542.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081633#comment-14081633
]
Prieur Leary commented on CLOUDSTACK-7217:
--
Looks like that is it.
2014-07-31 22:50:41,937 INFO [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.4.0
2014-07-31 22:50:41,937 INFO [cloud.agent.AgentShell] (main:null)
agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
2014-07-31 22:50:41,947 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: instance
2014-07-31 22:50:41,947 DEBUG [cloud.agent.AgentShell] (main:null) Found
property: resource
2014-07-31 22:50:41,947 INFO [cloud.agent.AgentShell] (main:null) Defaulting
to using properties file for storage
2014-07-31 22:50:41,949 INFO [cloud.agent.AgentShell] (main:null) Defaulting
to the constant time backoff algorithm
2014-07-31 22:50:41,974 INFO [cloud.utils.LogUtils] (main:null) log4j
configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
2014-07-31 22:50:42,001 DEBUG [cloud.agent.AgentShell] (main:null) Checking to
see if agent.SecStorage.pid exists.
2014-07-31 22:50:42,006 DEBUG [cloud.utils.ProcessUtil] (main:null)
environment.properties could not be opened
2014-07-31 22:50:42,014 DEBUG [cloud.utils.ProcessUtil] (main:null) Executing:
bash -c echo $PPID
2014-07-31 22:50:42,025 DEBUG [cloud.utils.ProcessUtil] (main:null) Execution
is successful.
2014-07-31 22:50:42,031 ERROR [cloud.agent.AgentShell] (main:null) Unable to
start agent: Resource class not found:
com.cloud.storage.resource.PremiumSecondaryStorageResource due to:
java.lang.Cla$
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081636#comment-14081636
]
Erik Weber commented on CLOUDSTACK-7217:
New rpms at https://www.dropbox.com/sh/x3zjvwy5ca1gpcu/AADsyYTYNQ6WOPoDvKbbnot2a
you'll have to force update since it's the same version..
rpm -Uvh --force cloudstack-*
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
[jira] [Created] (CLOUDSTACK-7219) Cannot display Cluster Settings after 4.4 Upgrade
Prieur Leary created CLOUDSTACK-7219: Summary: Cannot display Cluster Settings after 4.4 Upgrade Key: CLOUDSTACK-7219 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7219 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM, Management Server Affects Versions: 4.4.0 Environment: CentOS 6, KVM Hypervisor Reporter: Prieur Leary After upgrading MS to 4.4, when you to go: Home - Infrastructure - Clusters - Cluster 1 - Settings It does not display the settings underneath the column heading just, ERROR. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7209) [Automation] NPE observed in the CI Simulator Run on master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-7209: -- Priority: Critical (was: Blocker) [Automation] NPE observed in the CI Simulator Run on master --- Key: CLOUDSTACK-7209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Environment: CI Reporter: Raja Pullela Assignee: Alena Prokharchyk Priority: Critical Following NPE is observed on the CI Env: 02:17:16,156 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-72:ctx-6d23d8df job-215/job-216 ctx-cb3c4a4d) Lock is released for network Ntwk[222|Guest|11] as a part of network shutdown 2014-07-28 02:17:16,156 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Work-Job-Executor-72:ctx-6d23d8df job-215/job-216 ctx-cb3c4a4d) Lock is released for network id 222 as a part of network implement 2014-07-28 02:17:16,158 WARN [c.c.n.r.VpcVirtualNetworkApplianceManagerImpl] (Work-Job-Executor-72:ctx-6d23d8df job-215/job-216 ctx-cb3c4a4d) Failed to add router VM[DomainRouter|r-38-VM] to network Ntwk[222|Guest|11] due to java.lang.NullPointerException at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.createNicForVm(NetworkOrchestrator.java:3077) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateAddVmToNetwork(VirtualMachineManagerImpl.java:3409) at com.cloud.vm.VirtualMachineManagerImpl.addVmToNetwork(VirtualMachineManagerImpl.java:3355) at com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.addVpcRouterToGuestNetwork(VpcVirtualNetworkApplianceManagerImpl.java:267) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy191.addVpcRouterToGuestNetwork(Unknown Source) at com.cloud.network.element.VpcVirtualRouterElement.implement(VpcVirtualRouterElement.java:187) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetworkElementsAndResources(NetworkOrchestrator.java:1088) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:995) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1282) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:985) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5146) at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5302) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at
[jira] [Updated] (CLOUDSTACK-7018) Restore VM - missing destroyed usage event and decrementing resource count for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7018: Fix Version/s: 4.5.0 Restore VM - missing destroyed usage event and decrementing resource count for volume - Key: CLOUDSTACK-7018 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7018 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Priority: Critical Fix For: 4.5.0 Restore VM - missing destroyed usage event and decrementing resource count for volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7217) Cannot launch VM after 4.4 Upgrade on KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081670#comment-14081670
]
Prieur Leary commented on CLOUDSTACK-7217:
--
Seems to be working thus far. Will update here if something different.
Cannot launch VM after 4.4 Upgrade on KVM
-
Key: CLOUDSTACK-7217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: KVM, Management Server
Affects Versions: 4.4.0
Environment: CentOS 6
Reporter: Prieur Leary
Priority: Critical
Cannot launch VM after 4.4 upgrade.
Management server logs following:
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
cpu from host: 15, old used: 25500,reserved: 0, actual total$
2014-07-31 15:43:21,111 DEBUG [c.c.c.CapacityManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) release
mem from host: 15, old used: 37044092928,reserved: 0, total:$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564)
Invocation exception, caused by: com.cloud.exception.AgentUnavaila$
2014-07-31 15:43:21,183 INFO [c.c.v.VmWorkJobHandlerProxy]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053 ctx-1c0b8564) Rethrow
exception com.cloud.exception.AgentUnavailableException: R$
2014-07-31 15:43:21,183 DEBUG [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Done with run of VM
work job: com.cloud.vm.VmWorkStart for VM 3783, job origin: 3$
2014-07-31 15:43:21,183 ERROR [c.c.v.VmWorkJobDispatcher]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Unable to complete
AsyncJobVO {id:31053, userId: 1, accountId: 1, instanceType: n$
com.cloud.exception.AgentUnavailableException: Resource [Host:15] is
unreachable: Host 15: Unable to start instance due to Unable to get answer
that is of class com.cloud.agent.api.StartAnswer
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1105)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5190)
at sun.reflect.GeneratedMethodAccessor296.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5335)
at
com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:503)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:460)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to get
answer that is of class com.cloud.agent.api.StartAnswer
at com.cloud.agent.manager.Commands.getAnswer(Commands.java:80)
at
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1019)
... 19 more
2014-07-31 15:43:21,185 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Work-Job-Executor-157:ctx-089a5f26 job-30485/job-31053) Complete async
job-31053, jobStatus: FAILED, resultCode: 0, result: rO0ABXN$
2014-07-31 15:43:21,252 DEBUG [c.c.s.StatsCollector]
(StatsCollector-2:ctx-e03eec0e) VmStatsCollector is running...
2014-07-31 15:43:21,281 DEBUG
[jira] [Commented] (CLOUDSTACK-6594) Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081679#comment-14081679 ] ASF subversion and git services commented on CLOUDSTACK-6594: - Commit e26855e2849960951fd27fcb394c19a5b4bb2755 in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e26855e ] CLOUDSTACK-6594: Improve the logging in the util functions utilized by db upgrades currently. If the exception is to be ignored, dont log the stack trace and also dont log it in warn. Making them debug just to be little verbose during upgrade scenario. Correcting all the unit tests accordingly. Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists --- Key: CLOUDSTACK-6594 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6594 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: RHEL 6.3, Build - 4.4-forward, Also Ubuntu 14.04, CS 4.4.0-snapshot 20140513 Reporter: Rayees Namathponnan Assignee: Nitin Mehta Priority: Critical Fix For: 4.4.0 Attachments: CLOUDSTACK-6594.rar, management-server.log Below exception observed while staring MS INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) Loading module context [system] from URL [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-core-4.4.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml] INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 29066118877352 INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 29066118877352 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@883ca2e INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade. INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code Version = 4.4.0-SNAPSHOT INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.0.0 to 4.4.0-SNAPSHOT WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'last_sent'; check that column/key exists at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.upgrade.dao.DatabaseAccessObject.dropKey(DatabaseAccessObject.java:37) at com.cloud.upgrade.dao.DbUpgradeUtils.dropKeysIfExist(DbUpgradeUtils.java:28) at com.cloud.upgrade.dao.Upgrade410to420.addIndexForAlert(Upgrade410to420.java:543) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:98) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:310) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:432)
[jira] [Resolved] (CLOUDSTACK-6594) Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-6594. - Resolution: Fixed Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists --- Key: CLOUDSTACK-6594 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6594 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: RHEL 6.3, Build - 4.4-forward, Also Ubuntu 14.04, CS 4.4.0-snapshot 20140513 Reporter: Rayees Namathponnan Assignee: Nitin Mehta Priority: Critical Fix For: 4.4.0 Attachments: CLOUDSTACK-6594.rar, management-server.log Below exception observed while staring MS INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) Loading module context [system] from URL [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-core-4.4.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml] INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 29066118877352 INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 29066118877352 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@883ca2e INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade. INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code Version = 4.4.0-SNAPSHOT INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.0.0 to 4.4.0-SNAPSHOT WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'last_sent'; check that column/key exists at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.upgrade.dao.DatabaseAccessObject.dropKey(DatabaseAccessObject.java:37) at com.cloud.upgrade.dao.DbUpgradeUtils.dropKeysIfExist(DbUpgradeUtils.java:28) at com.cloud.upgrade.dao.Upgrade410to420.addIndexForAlert(Upgrade410to420.java:543) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:98) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:310) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:432) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at
[jira] [Updated] (CLOUDSTACK-6594) Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6594: Fix Version/s: (was: 4.4.0) 4.5.0 Observed many DB Exception while starting MS Can't DROP 'last_sent'; check that column/key exists --- Key: CLOUDSTACK-6594 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6594 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: RHEL 6.3, Build - 4.4-forward, Also Ubuntu 14.04, CS 4.4.0-snapshot 20140513 Reporter: Rayees Namathponnan Assignee: Nitin Mehta Priority: Critical Fix For: 4.5.0 Attachments: CLOUDSTACK-6594.rar, management-server.log Below exception observed while staring MS INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:null) Loading module context [system] from URL [jar:file:/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/cloud-core-4.4.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml] INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false INFO [c.c.u.d.Merovingian2] (main:null) Cleaning up locks for 29066118877352 INFO [c.c.u.d.Merovingian2] (main:null) Released 0 locks for 29066118877352 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@883ca2e INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade. INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.0.0 Code Version = 4.4.0-SNAPSHOT INFO [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.0.0 to 4.4.0-SNAPSHOT WARN [c.c.u.d.DatabaseAccessObject] (main:null) Ignored SQL Exception when trying to drop key last_sent on table alert com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Can't DROP 'last_sent'; check that column/key exists at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at com.cloud.upgrade.dao.DatabaseAccessObject.dropKey(DatabaseAccessObject.java:37) at com.cloud.upgrade.dao.DbUpgradeUtils.dropKeysIfExist(DbUpgradeUtils.java:28) at com.cloud.upgrade.dao.Upgrade410to420.addIndexForAlert(Upgrade410to420.java:543) at com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:98) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:310) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:432) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55) at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167) at org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51) at
[jira] [Reopened] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan reopened CLOUDSTACK-7012: - Still htting this issue with 4.5 build [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.4.0 Attachments: catalina.rar This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7220) [Hyper-V] Hyper-V Agent is broken in 4.4 branch
Anshul Gangwar created CLOUDSTACK-7220: -- Summary: [Hyper-V] Hyper-V Agent is broken in 4.4 branch Key: CLOUDSTACK-7220 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7220 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Anshul Gangwar Assignee: Anshul Gangwar While cherry picking commits are not applied in correct order -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7220) [Hyper-V] Hyper-V Agent is broken in 4.4 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-7220: --- Priority: Blocker (was: Major) [Hyper-V] Hyper-V Agent is broken in 4.4 branch --- Key: CLOUDSTACK-7220 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7220 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Anshul Gangwar Assignee: Anshul Gangwar Priority: Blocker While cherry picking commits are not applied in correct order -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7220) [Hyper-V] Hyper-V Agent is broken in 4.4 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-7220: --- Status: Reviewable (was: In Progress) [Hyper-V] Hyper-V Agent is broken in 4.4 branch --- Key: CLOUDSTACK-7220 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7220 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Anshul Gangwar Assignee: Anshul Gangwar Priority: Blocker While cherry picking commits are not applied in correct order -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7220) [Hyper-V] Hyper-V Agent is broken in 4.4 branch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081929#comment-14081929 ] Anshul Gangwar commented on CLOUDSTACK-7220: Patch is available for review at https://reviews.apache.org/r/24174/ [Hyper-V] Hyper-V Agent is broken in 4.4 branch --- Key: CLOUDSTACK-7220 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7220 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Anshul Gangwar Assignee: Anshul Gangwar Priority: Blocker While cherry picking commits are not applied in correct order -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7221) [Automation] Failed to start ManagementServer with latest 4.5 build
Rayees Namathponnan created CLOUDSTACK-7221: --- Summary: [Automation] Failed to start ManagementServer with latest 4.5 build Key: CLOUDSTACK-7221 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7221 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.5.0 Create RPM build from master branch, install, and start MS Management server failed to start with below error 2014-07-31 21:50:29,382 INFO [o.a.c.e.o.NetworkOrchestrator] (main:null) Network Manager is configured. 2014-07-31 21:50:29,387 DEBUG [c.c.a.m.AgentManagerImpl] (main:null) Registering listener StorageCapacityListener with id 3 2014-07-31 21:50:29,388 DEBUG [c.c.a.m.AgentManagerImpl] (main:null) Registering listener ComputeCapacityListener with id 4 2014-07-31 21:50:29,396 INFO [o.a.c.s.SecondaryStorageManagerImpl] (main:null) Start configuring secondary storage vm manager : PremiumSecondaryStorageManagerImpl 2014-07-31 21:50:29,701 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: 1000 2014-07-31 21:50:42,531 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_4f69b2af 2014-07-31 21:50:42,546 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_e4742209 2014-07-31 21:50:42,547 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_11b1201 2014-07-31 21:50:42,547 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MultipartMetaDaoImpl_EnhancerByCloudStack_e88394c0 2014-07-31 21:50:42,547 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.UserCredentialsDaoImpl_EnhancerByCloudStack_a21cdd20 2014-07-31 21:50:42,548 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackConfigurationDaoImpl_EnhancerByCloudStack_104f24de 2014-07-31 21:50:42,552 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.BucketPolicyDaoImpl_EnhancerByCloudStack_67e98ea3 2014-07-31 21:50:42,552 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SObjectItemDaoImpl_EnhancerByCloudStack_4bfc466c 2014-07-31 21:50:42,553 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MHostMountDaoImpl_EnhancerByCloudStack_a0ff7a7b -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7221) [Automation] Failed to start ManagementServer with latest 4.5 build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-7221: Attachment: management-server.log [Automation] Failed to start ManagementServer with latest 4.5 build --- Key: CLOUDSTACK-7221 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7221 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.5.0 Attachments: management-server.log Create RPM build from master branch, install, and start MS Management server failed to start with below error 2014-07-31 21:50:29,382 INFO [o.a.c.e.o.NetworkOrchestrator] (main:null) Network Manager is configured. 2014-07-31 21:50:29,387 DEBUG [c.c.a.m.AgentManagerImpl] (main:null) Registering listener StorageCapacityListener with id 3 2014-07-31 21:50:29,388 DEBUG [c.c.a.m.AgentManagerImpl] (main:null) Registering listener ComputeCapacityListener with id 4 2014-07-31 21:50:29,396 INFO [o.a.c.s.SecondaryStorageManagerImpl] (main:null) Start configuring secondary storage vm manager : PremiumSecondaryStorageManagerImpl 2014-07-31 21:50:29,701 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: 1000 2014-07-31 21:50:42,531 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_4f69b2af 2014-07-31 21:50:42,546 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_e4742209 2014-07-31 21:50:42,547 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_11b1201 2014-07-31 21:50:42,547 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MultipartMetaDaoImpl_EnhancerByCloudStack_e88394c0 2014-07-31 21:50:42,547 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.UserCredentialsDaoImpl_EnhancerByCloudStack_a21cdd20 2014-07-31 21:50:42,548 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackConfigurationDaoImpl_EnhancerByCloudStack_104f24de 2014-07-31 21:50:42,552 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.BucketPolicyDaoImpl_EnhancerByCloudStack_67e98ea3 2014-07-31 21:50:42,552 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SObjectItemDaoImpl_EnhancerByCloudStack_4bfc466c 2014-07-31 21:50:42,553 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.MHostMountDaoImpl_EnhancerByCloudStack_a0ff7a7b -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7214) [LDAP] connection timeout is hardcoded to 500ms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14081946#comment-14081946 ] ASF subversion and git services commented on CLOUDSTACK-7214: - Commit f7c664fc2e42854c306f206e0439df5038750db5 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f7c664f ] Revert Fixed bug: CLOUDSTACK-7214 added a config for ldap connection read timeout. This reverts commit cd2f27a6628472b1c0a6289989dc802f534ec74e. reverting it as it breaks the build when encryption is enabled. [LDAP] connection timeout is hardcoded to 500ms --- Key: CLOUDSTACK-7214 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7214 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Reporter: Rajani Karuturi Assignee: Rajani Karuturi Fix For: 4.5.0 if the ldap connection takes more than 500ms to respond, it timeout and doesnt return any users. There is no way to change this value from a configuration. -- This message was sent by Atlassian JIRA (v6.2#6252)
