Public bug reported:
Swap volume can't rollback correctly when get_volume_connector got exception
due to multipathd problem.
This will lead to old volume's status as retyping.
We can reproduce this problem:
1.Manufacturing multipathd service exception.
2.Execute volume retype operation while volume's status is in-use.
3.Check nova-compute service logs and got get_volume_connector error.
4.The volume will always be retyping.
Expected result:
The retyped volume's status should be in-use.
Actual result:
The retyped volume's status always be retyping.
** Affects: nova
Importance: Undecided
Status: 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/2103672
Title:
swap volume can not rollabck
Status in OpenStack Compute (nova):
New
Bug description:
Swap volume can't rollback correctly when get_volume_connector got exception
due to multipathd problem.
This will lead to old volume's status as retyping.
We can reproduce this problem:
1.Manufacturing multipathd service exception.
2.Execute volume retype operation while volume's status is in-use.
3.Check nova-compute service logs and got get_volume_connector error.
4.The volume will always be retyping.
Expected result:
The retyped volume's status should be in-use.
Actual result:
The retyped volume's status always be retyping.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2103672/+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
