Public bug reported:
Live-migration one instance, if not give destination host, disabled
nova-compute node will not be scheduled.but if give a disabled nova-
compute node as the destination host, the migration will execute. What
is the consideration of this inconsistent behavior?
It's better that the disabled nova-compute node shouldn't migrate in any
instances.
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
- Live-migration one instance, if not give destination host, disabled
nova-compute node will not be scheduled.
- but if give a disabled nova-compute node as the destination host, the
migration will execute.
- What is the consideration of this inconsistent behavior?
+ Live-migration one instance, if not give destination host, disabled
+ nova-compute node will not be scheduled.but if give a disabled nova-
+ compute node as the destination host, the migration will execute. What
+ is the consideration of this inconsistent behavior?
It's better that the disabled nova-compute node shouldn't migrate in any
instances.
--
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/1709242
Title:
inconsistent -behavior-for-live-migration
Status in OpenStack Compute (nova):
New
Bug description:
Live-migration one instance, if not give destination host, disabled
nova-compute node will not be scheduled.but if give a disabled nova-
compute node as the destination host, the migration will execute. What
is the consideration of this inconsistent behavior?
It's better that the disabled nova-compute node shouldn't migrate in
any instances.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1709242/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
