yahoo-eng-team team mailing list archive

[Luo Gangyi <luogangyi@xxxxxxxxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1562266

Title:
  VMware: resize instance change instance's  hypervisor_hostname

Status in OpenStack Compute (nova):
  Confirmed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1562266/+subscriptions