if all backend down, the status of share will stuck in "extending" when we extend an share

Bug #1855391 reported by haixin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Medium
haixin

Bug Description

In the process of extending share, i found extend share api use rpc direct call share manager to execute extend. But if manila-share lose connection to backend storage or manila-share service is down. the status of share will stuck in extending. This is an intermediate state, So I don't think that's reasonable.
i think we can use scheduler layer instead of direct call share manager, if allocation backend failed, the status of share will rollback to "available". and user messages will record this anomaly, which will help user to know why extend share not success.

haixin (haixin77)
Changed in manila:
assignee: nobody → haixin (haixin77)
summary: - if all backend down, the status of share will always "extending" when we
- extend an share
+ if all backend down, the status of share will stuck in "extending" when
+ we extend an share
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master
Review: https://review.opendev.org/700393

Changed in manila:
status: New → In Progress
Changed in manila:
importance: Undecided → Medium
importance: Medium → High
Vida Haririan (vhariria)
Changed in manila:
milestone: none → victoria-1
Revision history for this message
Vida Haririan (vhariria) wrote :
Revision history for this message
Vida Haririan (vhariria) wrote :
Revision history for this message
Maurice Escher (maurice-escher) wrote :
Changed in manila:
milestone: victoria-1 → victoria-2
Changed in manila:
milestone: victoria-2 → victoria-3
Changed in manila:
milestone: victoria-3 → victoria-rc1
Changed in manila:
milestone: victoria-rc1 → wallaby-1
Changed in manila:
milestone: wallaby-1 → wallaby-2
importance: High → Medium
Changed in manila:
milestone: wallaby-2 → wallaby-3
Revision history for this message
Vida Haririan (vhariria) wrote :
tags: added: wallaby-rc-bugsquash
Changed in manila:
milestone: wallaby-3 → wallaby-rc1
Changed in manila:
milestone: wallaby-rc1 → xena-1
tags: removed: wallaby-rc-bugsquash
Revision history for this message
Goutham Pacha Ravi (gouthamr) wrote :

Fix proposed to branch master:
    https://review.opendev.org/c/openstack/manila/+/700393

Changed in manila:
milestone: xena-1 → xena-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.opendev.org/c/openstack/manila/+/700393
Committed: https://opendev.org/openstack/manila/commit/cdbc428b692ca087e26fa1ab5c3d1f5fb77cdc29
Submitter: "Zuul (22348)"
Branch: master

commit cdbc428b692ca087e26fa1ab5c3d1f5fb77cdc29
Author: haixin <email address hidden>
Date: Mon Dec 23 16:33:04 2019 +0800

    Extend share will go through scheduler

    Add an force parameter to the API layer that lets the user choose
    whether to go through the scheduler or not, which is boolean.and
    default is False,set True means extend share directly, set False
    means extend share will go through scheduler.
    Add an new min_version 2.64 to extend share api. force parameter
    only support min_version >= 2.64.

    Closes-Bug:#1855391
    Change-Id: I6da36a687a37c78a7fb7d3f252318d03d4a05133

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 13.0.0.0rc1

This issue was fixed in the openstack/manila 13.0.0.0rc1 release candidate.

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.