1509398: Add retry to iSCSI delete
Bug #1521645 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:/
Looks like there might be a race in trying to delete a target immediately after a logout. I've seen this a couple times in my CI system this week, but it certainly doesn't seem at all prevalent.
| Changed in mos: | |
| milestone: | none → 7.0-mu-2 |
| Changed in mos: | |
| milestone: | 7.0-mu-2 → 7.0-updates |
Revision history for this message
| Alexey Stupnikov (astupnikov) wrote | #1 |
| 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 | #2 |
To post a comment you must log in.
Original issue contains information that there is an issue with disconnecting iSCSI volumes from ironic slave nodes. There is no ironic system in MOS 7.0, but issue with brick could be there.
Initial bug contains information that 'Attempting to delete an iSCSI target immediately after the initiator has logged out of the session can sometimes cause iscsiadm's database update to fail.' with error 'Stderr: 'iscsiadm: Could not execute operation on all records: encountered iSCSI database failure\n''
I have repeatedly connected volume to VM and then disconnected it without specified error. I have manually connected and disconnected iscsi targets 100 times without specified error.
That is why I consider this bug for MOS 7.0 as Incomplete and will merge its patch only as a part of a dependency resolution process.