1509398: Prevent missing Purity hosts from raising errors
Bug #1521642 reported by
Alexey Stupnikov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Invalid
|
High
|
Alexey Stupnikov | ||
| 7.0.x |
Won't Fix
|
High
|
Alexey Stupnikov | ||
Bug Description
This is a "sub-bug" of https:/
Occasionally a Purity host can be deleted out from underneath Cinder. When this happens if cinder is attempting to disconnect a volume from that host we should treat it as a ‘success’ since if the host is gone, it is disconnected already (as far as Purity is concerned).
To prevent one cause of this, the disconnect method will now be locked with the connect ones so that can’t delete a host we intend to re-use.
Upstream bug: https:/
| Changed in mos: | |
| assignee: | nobody → Alexey Stupnikov (astupnikov) |
| milestone: | none → 7.0-mu-2 |
| Changed in mos: | |
| milestone: | 7.0-mu-2 → 7.0-updates |
| Changed in mos: | |
| milestone: | 7.0-updates → 8.0 |
| status: | Confirmed → New |
| Changed in mos: | |
| status: | New → Invalid |
Revision history for this message
| Alexey Stupnikov (astupnikov) wrote | #1 |
To post a comment you must log in.
Won't fix, as we don't accept partner features to MOS7 anymore.