Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 11 Feb 2014 14:21:22 +0000 (UTC)
From: "sadhu suresh (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12682654.1386155071001.23800.1392128482763@arcas>
In-Reply-To: <JIRA.12682654.1386155071001@arcas>
References: <JIRA.12682654.1386155071001@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-5363) kvm:vmsync:vm state still show
 running even after host is poweredoff
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

sadhu suresh resolved CLOUDSTACK-5363.
--------------------------------------

    Resolution: Cannot Reproduce

Thanks abhi,tested with new build  and not able to reproduce the issue so closing the issue.

> kvm:vmsync:vm state still show running even after host is poweredoff
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5363
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5363
>             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: sadhu suresh
>             Fix For: 4.3.0
>
>
> STEPS:
> 1.Create an advanced zone with 2  kvm hosts
> 2.deploy  2 vms
> 3.migrae a vm from  host1 to host2
> 4.once migration completed,power of the  host2
> 5.check the vm state& host state
> actual result:
> Vm state still shows running even after power off the host.
> host state is disconnected*vm state is running.
> mysql> select * from vm_instance where id=3\G;
> *************************** 1. row ***************************
>                       id: 3
>                     name: VM1sadhu
>                     uuid: 1ccb132a-55b2-48e3-b07d-42f8aa81255c
>            instance_name: i-3-3-VM
>                    state: Running
>           vm_template_id: 4
>              guest_os_id: 112
>      private_mac_address: NULL
>       private_ip_address: NULL
>                   pod_id: 1
>           data_center_id: 1
>                  host_id: 5
>             last_host_id: 1
>                 proxy_id: 2
>        proxy_assign_time: 2013-12-02 13:33:58
>             vnc_password: DfZpD3rXt3L7bwjPxxRXTrMUfP37mznhRFPZDVWc0YY=
>               ha_enabled: 0
>            limit_cpu_use: 0
>             update_count: 32
>              update_time: 2013-12-04 15:54:07
>                  created: 2013-12-02 12:59:12
>                  removed: NULL
>                     type: User
>                  vm_type: User
>               account_id: 3
>                domain_id: 1
>      service_offering_id: 1
>           reservation_id: 16fb58da-3e58-4039-ba17-d1c65f21c94c
>          hypervisor_type: KVM
>         disk_offering_id: NULL
>                      cpu: NULL
>                      ram: NULL
>                    owner: 3
>                    speed: 500
>                host_name: VM1sadhu
>             display_name: VM1sadhu
>            desired_state: NULL
>     dynamically_scalable: 0
>               display_vm: 1
>              power_state: NULL
>  power_state_update_time: NULL
> power_state_update_count: 0
>               power_host: NULL


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