2 year old bug, that was reported fixed in grizzly
** Changed in: nova
Status: Incomplete => Invalid
--
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/1163252
Title:
MIGRATING status doesn't reset when an InvalidSharedStorage ERROR
occurred.
Status in OpenStack Compute (Nova):
Invalid
Bug description:
MIGRATING status doesn't reset when an InvalidSharedStorage ERROR
occurred.
It seems that deserialize_remote_exception
method(nova/openstack/common/rpc/common.py) create an
InvalidSharedStorage_Remote ERROR dynamically from an
InvalidSharedStorage ERROR,so nova-scheduler can not catch an
InvalidSharedStorage ERROR.
nova-scheduler should catch an InvalidSharedStorage_Remote Error to
reset MIGRATING status.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1163252/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
