Mirantis OpenStack

On controller failure, some RBD backed Cinder volumes may become unmanageable

  1. Series 6.0.x
  2. Bug #1371328
Bug #1371328 reported by Dmitry Borodaenko
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Committed
Medium
Dmitry Borodaenko
Mirantis OpenStack 5.1.1
5.0.x
Fix Committed
Medium
Dmitry Borodaenko
Mirantis OpenStack 5.0-updates
5.1.x
Fix Committed
Medium
Dmitry Borodaenko
Mirantis OpenStack 5.1.1
6.0.x
Fix Committed
Medium
Dmitry Borodaenko
Mirantis OpenStack 6.0

Bug Description

According to upstream bug #1028718 and bug #1280367, cinder-volume associates volume metadata with specific host (node where cinder-volume service is running), and will refuse to manage (attach/detach/delete) volumes that are associated with that host.

Based on comments in bug #1280367, setting host variable in cinder.conf to the same value on all controllers would resolve this limitation as long as multiple backends are not enabled. If that workaround is confirmed, this bug can be downgraded to Medium.

Revision history for this message
Irina Povolotskaya (ipovolotskaya) wrote :

Should this be included into Release notes?
Can the abovementioned workaround be confirmed?

Dmitry Borodaenko (angdraug)
Changed in mos:
status: New → Confirmed
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

The workaround is confirmed and implemented in fuel-library commit https://review.openstack.org/122907.

Since we're in hard code freeze and will not be including this commit in 5.1, please add this to 5.1 release notes as a known issue.

tags: added: release-notes
Changed in mos:
importance: High → Medium
Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Dmitry B: why did you change the status of that bug for all the series? Though there was a workaround applied, I assume we still want a proper fix, don't we?

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

The workaround for 5.1 was to apply the patch linked above (https://review.openstack.org/122907) manually, since it didn't make it into 5.1 GA due to code freeze. That patch has now been merged to master and stable/5.1 and will be included in 5.1.1 GA and 6.0 GA releases, that's why the status for these is set to Fix Committed. A version of that patch has also been proposed for stable/5.0, until it's merged the status there should remain In Progress.

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Dmitry B: aha, I see. Thank you for clarification. Another thing is, since you are working on fixes, the bug should be reassigned to you. Otherwise, cinder team might confusingly think nobody works on it so far. If you agree, please reassign to yourself in all the series.

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Fix for stable/5.0 was merged in: https://review.openstack.org/129969

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.