angeline shen created CLOUDSTACK-4526:
-----------------------------------------

             Summary: [Vmware] new mapping vmware datacenter cloudstack zone - 
VM host migration across cluster FAIL
                 Key: CLOUDSTACK-4526
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4526
             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
            Priority: Critical
             Fix For: 4.2.0


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 

5. VM  i-2-4-VM  host migration from 10.223.51.2 in cluster 1 to 10.223.51.4 in 
cluster 2 FAIL



--
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

Reply via email to