cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-2112) VM went in stopped state after live migratin failed while vmscaleup
Date Fri, 19 Apr 2013 09:53:16 GMT
prashant kumar mishra created CLOUDSTACK-2112:

             Summary: VM went in stopped state after  live migratin failed while vmscaleup
                 Key: CLOUDSTACK-2112
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
            Reporter: prashant kumar mishra
             Fix For: 4.2.0

Setup is on top of commit "2057221f4f1fd5afde422b367fc416d4e44275cb "

Vm went in stopped state when migration failed while scaling up .

Step to reproduce
1-Create zone ,pod ,cluster with one host
2-Deploy vms so that no resource left on host
3-Add another host to same cluster
4-Try Scaleup vm from small instance to medium instance
5-Since no resource available on current host CS will try to live migrate vm
6-power of target host

vm should remain running state even after scaleup failure

VM went in stooped state

Snippet of MS log
2013-04-19 10:57:16,443 DEBUG [cloud.capacity.CapacityManagerImpl] (HA-Worker-0:work-3) VM
state transitted from :Migrating to Stopped with event: AgentReportStoppedvm's original host
id: 1 new host id: null host id before state transition: 10

013-04-19 10:59:17,556 WARN  [xen.resource.CitrixResourceBase] (DirectAgent-19:null) Unable
to migrate VM(i-2-33-VM) from host(57d25f98-9aad-4c3a-9c34-9b663ae0c95f) due to Task failed!
Task record:                 uuid: 806bc37d-b495-8554-4b60-e3a8218c1fbd

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message