[
https://issues.apache.org/jira/browse/CLOUDSTACK-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073776#comment-14073776
]
Rayees Namathponnan commented on CLOUDSTACK-7179:
-------------------------------------------------
I can see primary storages in good state now
[root@Rack2Host11 agent]# mount
/dev/sda2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
nfs1-ccp.citrix.com:/home/common/automation/SC_QA_AUTO4/primary2 on
/mnt/e9b0d73b-9890-3aae-8934-44bd194592e0 type nfs
(rw,noac,actimeo=0,vers=4,addr=10.223.240.164,clientaddr=10.223.50.66)
nfs1-ccp.citrix.com:/home/common/automation/SC_QA_AUTO4/primary on
/mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc type nfs
(rw,noac,actimeo=0,vers=4,addr=10.223.240.164,clientaddr=10.223.50.66)
[root@Rack2Host11 agent]# cd /mnt/e9b0d73b-9890-3aae-8934-44bd194592e0
[root@Rack2Host11 e9b0d73b-9890-3aae-8934-44bd194592e0]# ls
10e29d9f-6950-4993-a654-6bd8bc7afd03 532e314f-746a-43e0-9073-253c4c58a4a4
abdcea2e-a90d-4727-80fe-e70035baff47
1f5ceccd-bc65-47d3-aace-d4d0b4bbf5f4 5e9b6182-8f74-440d-b95d-4df761304fd1
af10c3eb-ffde-4468-8cbb-b3fb78d4c243
2493d5fe-82c0-4ea9-aebe-fce0c2be8369 68a91b13-21e5-4e02-9ae3-7f5fb90adbdf
b0108034-d80a-42eb-b2b7-a74ac56166e5
31dcb62e-9200-4669-9113-5c4f76233e76 7ce366e7-1fe4-4164-b493-8afe4d48b9f9
b80c54fa-55b0-408f-8281-dc1923a73d8c
36075a10-1c9f-4653-8895-e8c592ea23db 7ee7471e-a681-4a47-92b5-1c074ba61fb3
be93c338-b3a7-49a1-9acd-02cc67dc2500
37f82fa0-3f12-4b84-8a98-53dc3f1e448d 8610a779-035b-41e4-b391-efae1aedb315
c59e2fcc-6325-4071-b90b-ed9612aac28b
380598b1-27bd-4e23-a895-dd8a1142d112 866ace2c-726c-49cb-9924-71bb06558070
cdfedf0f-4df9-4671-99d7-2dab703a1220
3992016b-c1ed-4f16-921f-2309ee94473d 9d0da2c6-f4e7-4607-b473-ba5459ed2eb3
fd0d8220-b52f-4984-9201-9f4b29aedd68
3ddd95f4-752a-4b72-9398-00f66c852f59 9fd46da7-924d-4e52-a2fb-52fbf945188b
KVMHA
3f16d0d0-79a7-4569-98ce-bd7993e5c527 a2cc149e-12a9-11e4-b040-1a6f7bb0d0a8
450e3b26-ac4b-490d-bbcc-61447d7a99a7 a2cc4694-12a9-11e4-b040-1a6f7bb0d0a8
[root@Rack2Host11 e9b0d73b-9890-3aae-8934-44bd194592e0]#
> [Automation] Router deployment failing while calling "patchviasocket.pl"
> during router configuration
> ----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7179
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7179
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.5.0
> Environment: KVM RHEL 6.3
> Reporter: Rayees Namathponnan
> Assignee: edison su
> Priority: Blocker
> Fix For: 4.5.0
>
>
> This issue is observed in automation environment, there are many router
> deployment failure, this issue observed while programming "patchviasocket.pl"
> 2014-07-23 22:50:23,660 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-5:null) Executing:
> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n
> r-384-VM -p
> %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
> 2014-07-23 22:50:24,973 DEBUG
> [resource.virtualnetwork.VirtualRoutingResource]
> (agentRequest-Handler-3:null) Trying to connect to 169.254.3.89
> 2014-07-23 22:50:27,974 DEBUG
> [resource.virtualnetwork.VirtualRoutingResource]
> (agentRequest-Handler-3:null) Could not connect to 169.254.3.89
> 2014-07-23 22:50:28,661 WARN [kvm.resource.LibvirtComputingResource]
> (Script-7:null) Interrupting script.
> 2014-07-23 22:50:28,662 WARN [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-5:null) Timed out:
> /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n
> r-384-VM -p
> %template=domP%name=r-384-VM%eth2ip=10.223.122.84%eth2mask=255.255.255.192%gateway=10.223.122.65%eth0ip=10.1.1.1%eth0mask=255.255.255.0%domain=csfeauto.advanced%cidrsize=24%dhcprange=10.1.1.1%eth1ip=169.254.1.76%eth1mask=255.255.0.0%type=router%disable_rp_filter=true%dns1=8.8.8.8
> . Output is:
> 2014-07-23 22:50:28,662 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-5:null) passcmd failed:timeout
> 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-3:null) Request:Seq 1-5899996986832060423: { Cmd ,
> MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"checkBeforeCleanup":true,"vmName":"r-384-VM","wait":0}}]
> }
> 2014-07-23 22:52:56,323 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-3:null) Processing command:
> com.cloud.agent.api.StopCommand
> 2014-07-23 22:52:56,326 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM,
> continue
> 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM,
> continue
> 2014-07-23 22:52:56,328 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then
> use the default hypervisor
> 2014-07-23 22:52:56,330 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Failed to get vm status in case of
> checkboforecleanup is true
> org.libvirt.LibvirtException: Domain not found: no domain with matching name
> 'r-384-VM'
> at org.libvirt.ErrorHandler.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.processError(Unknown Source)
> at org.libvirt.Connect.domainLookupByName(Unknown Source)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3506)
> at
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1276)
> 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-23 22:52:56,332 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-3:null) can't find connection: KVM, for vm: r-384-VM,
> continue
> 2014-07-23 22:52:56,334 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-3:null) can't find connection: LXC, for vm: r-384-VM,
> continue
> 2014-07-23 22:52:56,334 DEBUG [kvm.resource.LibvirtConnection]
> (agentRequest-Handler-3:null) can't find which hypervisor the vm used , then
> use the default hypervisor
> 2014-07-23 22:52:56,336 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Failed to get dom xml:
> org.libvirt.LibvirtException: Domain not found: no domain with matching name
> 'r-384-VM'
> 2014-07-23 22:52:56,337 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Failed to get dom xml:
> org.libvirt.LibvirtException: Domain not found: no domain with matching name
> 'r-384-VM'
> 2014-07-23 22:52:56,338 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Failed to get dom xml:
> org.libvirt.LibvirtException: Domain not found: no domain with matching name
> 'r-384-VM'
> 2014-07-23 22:52:56,338 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Executing:
> /usr/share/cloudstack-common/scripts/vm/network/security_group.py
> destroy_network_rules_for_vm --vmname r-384-VM
> 2014-07-23 22:52:56,535 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Execution is successful.
> 2014-07-23 22:52:56,536 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) Try to stop the vm at first
> 2014-07-23 22:52:56,537 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-3:null) VM r-384-VM doesn't exist, no need to stop it
> 2014-07-23 22:52:56,538 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-3:null) Seq 1-5899996986832060423: { Ans: , MgmtId:
> 29066118877352, via: 1, Ver: v1, Flags: 10,
> [{"com.cloud.agent.api.StopAnswer":{"result":true,"wait":0}}] }
> 2014-07-23 22:52:56,641 DEBUG [cloud.agent.Agent] (Agent-Handler-1:null)
> Received response: Seq 0-1: { Ans: , MgmtId: 29066118877352, via: 1, Ver:
> v1, Flags: 100010,
> [{"com.cloud.agent.api.PingAnswer":{"_command":{"hostType":"Routing","hostId":0,"wait":0},"result":true,"wait":0}}]
> }
> 2014-07-23 22:52:56,644 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-4:null) Request:Seq 1-5899996986832060424: { Cmd ,
> MgmtId: 29066118877352, via: 1, Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.CheckVirtualMachineCommand":{"vmName":"r-386-VM","wait":20}}]
> }
> 2014-07-23 22:52:56,644 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-4:null) Processing command:
> com.cloud.agent.api.CheckVirtualMachineCommand
--
This message was sent by Atlassian JIRA
(v6.2#6252)
