Multipath ignores map in use when flushing

Bug #1663936 reported by Gorka Eguileor
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-brick
Fix Released
Undecided
Gorka Eguileor

Bug Description

When flushing a multipath we are ignoring map in use transient error, so we log a warning that the flush has not been successful and that we have received an exit code 1 and we continue to remove the individual paths.

This error is usually transient and a simple retry will succeed in flushing the multipath.

Failure to retry will leave an empty multipath in our system.

Gorka Eguileor (gorka)
Changed in os-brick:
assignee: nobody → Gorka Eguileor (gorka)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-brick (master)

Fix proposed to branch: master
Review: https://review.openstack.org/433103

Changed in os-brick:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-brick (master)

Reviewed: https://review.openstack.org/433103
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=32c837dacb38910e9191b1a3f18283b3c52fb2b2
Submitter: Jenkins
Branch: master

commit 32c837dacb38910e9191b1a3f18283b3c52fb2b2
Author: Gorka Eguileor <email address hidden>
Date: Sat Feb 11 21:40:39 2017 +0100

    Retry multipath flush when map is in use

    When flushing a multipath we are ignoring map in use transient error, so
    we log a warning that the flush has not been successful and that we have
    received an exit code 1 and we continue to remove the individual paths.

    This error is usually transient and a simple retry will succeed in
    flushing the multipath.

    Failure to retry will leave an empty multipath in our system.

    Closes-Bug: #1663936
    Change-Id: I710792bd707ad933ef60d11d25f530dddfb6fb2f

Changed in os-brick:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-brick (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/445942

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-brick (stable/ocata)

Reviewed: https://review.openstack.org/445942
Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=04c4d07dc4471fe4e971835d8c3698c79f13ba17
Submitter: Jenkins
Branch: stable/ocata

commit 04c4d07dc4471fe4e971835d8c3698c79f13ba17
Author: Gorka Eguileor <email address hidden>
Date: Sat Feb 11 21:40:39 2017 +0100

    Retry multipath flush when map is in use

    When flushing a multipath we are ignoring map in use transient error, so
    we log a warning that the flush has not been successful and that we have
    received an exit code 1 and we continue to remove the individual paths.

    This error is usually transient and a simple retry will succeed in
    flushing the multipath.

    Failure to retry will leave an empty multipath in our system.

    Closes-Bug: #1663936
    Depends-On: I31310dc9b3834e0bf16618db3e473f17eab2b610
    Change-Id: I710792bd707ad933ef60d11d25f530dddfb6fb2f
    (cherry picked from commit 32c837dacb38910e9191b1a3f18283b3c52fb2b2)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-brick 1.12.0

This issue was fixed in the openstack/os-brick 1.12.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-brick 1.11.1

This issue was fixed in the openstack/os-brick 1.11.1 release.

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

Other bug subscribers

Remote bug watches

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