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
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
** Changed in: nova
Status: Invalid => New
--
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
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
4 matches
Mail list logo
