You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jayapal Reddy (JIRA)" <ji...@apache.org> on 2014/01/23 11:07:38 UTC

[jira] [Resolved] (CLOUDSTACK-5924) noticed qemu error in the logs during vms rules cleanup

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jayapal Reddy resolved CLOUDSTACK-5924.
---------------------------------------

    Resolution: Fixed

> noticed qemu error in the logs during vms rules cleanup
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-5924
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5924
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.3.0
>            Reporter: sadhu suresh
>            Assignee: Jayapal Reddy
>            Priority: Minor
>
> noticed below errors in the host logs during vms rules cleanup
> steps:
> put host in maintenance mode 
> check the host logs
> Received response: Seq 4-1355:  { Ans: , MgmtId: 7322717913215, via: 4, Ver: v1, Flags: 100010, [{"com.cloud.agent.api.PingAnswer":{"_command":{"hostType":"Routing","hostId":4,"wait":0},"result":true,"wait":0}}] }
> 2014-01-21 07:20:04,268 DEBUG [kvm.resource.KVMHAMonitor] (Thread-1355:null) Found NFS storage pool 81c8c822-016d-374f-b44b-18d84ba54499 in libvirt, continuing
> 2014-01-21 07:20:04,269 DEBUG [kvm.resource.KVMHAMonitor] (Thread-1355:null) Executing: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh -i 10.147.28.7 -p /export/home/sadhu/felton/primtest -m /mnt/81c8c822-016d-374f-b44b-18d84ba54499 -h 10.147.40.26
> 2014-01-21 07:20:04,287 DEBUG [kvm.resource.KVMHAMonitor] (Thread-1355:null) Execution is successful.
> 2014-01-21 07:20:22,428 DEBUG [kvm.resource.LibvirtComputingResource] (Agent-Handler-3:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py cleanup_rules
> 2014-01-21 07:20:24,984 DEBUG [kvm.resource.LibvirtComputingResource] (Agent-Handler-3:null) Execution is successful.
> 2014-01-21 07:20:24,985 DEBUG [kvm.resource.LibvirtComputingResource] (Agent-Handler-3:null) libvir: QEMU error : Domain not found: no domain with matching name 'i-2-10-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-10-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-8-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-8-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-3-3-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-3-3-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-7-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-7-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-9-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-2-9-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-5-13-VM-ips'
> libvir: QEMU error : Domain not found: no domain with matching name 'i-5-13-VM-ips'
> 2014-01-21 07:20:24,986 DEBUG [cloud.agent.Agent] (Agent-Handler-3:null) Watch Sent: Seq 4-329908226:  { Ans: , MgmtId: 7322717913215, via: 4, Ver: v1, Flags: 10, [{"com.cloud.agent.api.Answer":{"result":true,"details":"","wait":0}}] }
> 2014-01-21 07:21:01,715 DEBUG [kvm.resource.LibvirtComputingResource] (UgentTask-5:null) Executing: /usr/share/cloudstack-common/scripts/vm/network/security_group.py get_rule_logs_for_vms
> 2014-01-21 07:21:01,973 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) Processing command: com.cloud.agent.api.GetVmStatsCommand



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)