cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkata Siva Vijayendra Bhamidipati (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4513) [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC put in maintenance mode, CPVM and guest VMs that were migrated failed to come up
Date Wed, 28 Aug 2013 00:21:51 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751942#comment-13751942
] 

Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4513:
-----------------------------------------------------------------

In the logs, migration is constantly being retried and is failing because of insufficient
capacity for VM migration. Excerpt of one such failure from the log:

2013-08-26 11:35:12,124 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator)
Looking for hosts in dc: 1  pod:1  cluster:3
2013-08-26 11:35:12,128 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator)
FirstFitAllocator has 1 hosts to check for allocation: [Host[-6-Routing]]
2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator)
Found 1 hosts for allocation after prioritization: [Host[-6-Routing]]
2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator)
Looking for speed=100Mhz, Ram=512
2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator)
Host name: 10.223.51.4, hostId: 6 is in avoid set, skipping this and trying other available
hosts
2013-08-26 11:35:12,130 DEBUG [allocator.impl.FirstFitAllocator] (HA-Worker-0:work-1 FirstFitRoutingAllocator)
Host Allocator returning 0 suitable hosts
2013-08-26 11:35:12,130 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (HA-Worker-0:work-1)
No suitable hosts found
2013-08-26 11:35:12,130 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (HA-Worker-0:work-1)
No suitable hosts found under this Cluster: 3
2013-08-26 11:35:12,132 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] (HA-Worker-0:work-1)
Could not find suitable Deployment Destination for this VM under any clusters, returning.
2013-08-26 11:35:12,132 DEBUG [cloud.deploy.FirstFitPlanner] (HA-Worker-0:work-1) Searching
resources only under specified Cluster: 3
2013-08-26 11:35:12,133 DEBUG [cloud.deploy.FirstFitPlanner] (HA-Worker-0:work-1) The specified
cluster is in avoid set, returning.
2013-08-26 11:35:12,133 DEBUG [cloud.vm.VirtualMachineManagerImpl] (HA-Worker-0:work-1) Unable
to find destination for migrating the vm VM[User|z1vpc1G1adminV6]
2013-08-26 11:35:12,133 WARN  [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:work-1)
Insufficient capacity for migrating a VM.
2013-08-26 11:35:12,134 DEBUG [cloud.resource.ResourceManagerImpl] (HA-Worker-0:work-1) No
next resource state for host 6 while current state is Enabled with event UnableToMigrate
com.cloud.utils.fsm.NoTransitionException: No next resource state found for current state
=Enabled event =UnableToMigrate
    at com.cloud.resource.ResourceManagerImpl.resourceStateTransitTo(ResourceManagerImpl.java:1173)
    at com.cloud.resource.ResourceManagerImpl.maintenanceFailed(ResourceManagerImpl.java:2285)
    at com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:581)
    at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:829)
2013-08-26 11:35:12,134 INFO  [cloud.ha.HighAvailabilityManagerImpl] (HA-Worker-0:work-1)
Rescheduling HAWork[1-Migration-5-Running-Migrating] to try again at Mon Aug 26 11:37:14 PDT
2013



Angie, it looks like you are running into a capacity problem - can you retry this after adding
a third host in C1 to increase host capacity? Or, you could try using a smaller service offering
for the system/user VMs to see if this occurs with those.
                
> [Vmware] new mapping vmware datacenter cloudstack zone - Host in second cluster in DC
put in maintenance mode, CPVM and  guest VMs that were migrated failed to come up
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4513
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4513
>             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
>         Environment: MS    10.223.195.52     build  479
> host   ESXi 5.0
>            Reporter: angeline shen
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: management-server.log.gz, management-server.log.gz, Screenshot-CloudPlatform™
- Mozilla Firefox-1.png, Screenshot-CloudPlatform™ - Mozilla Firefox-2.png, Screenshot-CloudPlatform™
- Mozilla Firefox-9.png, Screenshot-CloudPlatform™ - Mozilla Firefox.png
>
>
> 1.  
> Vcenter                                  CPP 4.2.
> VC1 - DC1 -  C1 - H1             zone1 - C1 -  H1     10.223.51.2
>                             H2                               H2     10.223.51.3
>                                                                   PS2 cluster primary
storage
>                                                                   
>                     C2 - H3                        C2 -  H3     10.223.51.4
>                                                                   PS3 cluster primary
storage
>                                                                   PS1 zone primary storage
>                                                                   PSZ4 zone primary storage
> 2.  H3    10.223.51.4   has  SSVM  CPVM  and VMs  i-2-8    i-2-6
>      VRs and other guest VMs  were on Hosts H1  and H3
> 3.  Put H3 in maintenance mode.   
> Result:
>  VMs i-2-6-VM  and i-2-8-VM went into STOP state.  Try to start both VMs.  These remain
in 
> 'Starting' state .
> New SSVM s-14-VM created..  Old SSVM s-10-VM  remained in expunging and disconnected
state
> CPVM v-11-VM  remain in STOP and disconnected state.   Cannot be started
> 4. Host H3 cancel maintenance mode.
> Old SSVM s-10-VM  remained in expunging and disconnected state
> CPVM v-11-VM  go to running state
> Old SSVM s-10-VM  remained in expunging and disconnected state
> VMs i-2-6-VM  and i-2-8-VM were in STOP state.  
> Unable to restart both guest VMs - deployment failed
>     

--
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: http://www.atlassian.com/software/jira

Mime
View raw message