OpenStack Compute (nova)

VMware: resize instance change instance's hypervisor_hostname

Bug #1562266 reported by Dongcan Ye
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Wishlist
Unassigned

Bug Description

Nova version: master
Virt driver: VCDriver

Nova compute1 <--> VMware cluster1
Nova compute2 <--> VMware cluster2

Resize an instance(original hypervisor_hostname is domain-c9(cluster2)) in VMware, makes instance's hostname changed(Before we verify, hypervisor_hostname had changed to domain-c7(cluster1)).

Then we checked in vCenter, the instance still located in cluster2.

See original description
Tags: vmware
Dongcan Ye (hellochosen)
description: updated
Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

Well, the resize operation implies to reschedule the instance to a new host (given the flavor is different) than can possibly be the same host if the config option allow_resize_to_same_host is set to True (defaulted to False).

So, it's perfectly normal to have the hypervisor_hostname changed if you resize an instance.

Changed in nova:
status: New → Invalid
Revision history for this message
Dongcan Ye (hellochosen) wrote :

Thanks for your reply, Sylvain.
allow_resize_to_same_host option may not help for us, it also possible scheduled to another host.

There has one method to slove this problem. We need to judge the instance's hypervisor type, if the type is VMware, we should
 force scheduling to the same host when resize.

Dongcan Ye (hellochosen)
Changed in nova:
status: Invalid → New
Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

Not sure I understand your problem. I don't want Nova to have a different behaviour between different drivers. When resizing, it will go to the scheduler anyway so it could have a different destination.

If you want to only have the same destination for resizing, that looks like a new feature that people would want to get, not really a problem because your instance could still be okay if it would be in a different node.

Changed in nova:
importance: Undecided → Wishlist
status: New → Invalid
Revision history for this message
Luo Gangyi (luogangyi) wrote :

I met the same problem.

And I believe it is definitely a bug!

nova's behavior is inconsistent with vmware driver does. And it will cause all following operation fail!

If vmware do not support cross-cluster resize, we should force nova-scheduler choose the same cluster.

Changed in nova:
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.