Cinder

SolidFire driver can fail to clone due timeout

Bug #1898587 reported by Fernando Ferraz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Fernando Ferraz

Bug Description

When cloning a volume in solidfire.py there is a module "_get_model_info" in here is a hardcoded retry count of 600. Customers are facing timeout issues when volumes are too big (ie. multi-terabyte volumes), due to poor networks or upgrade issues that revolve around the ElementOS cluster. A viable solution is to make this value configurable in cinder.conf, to allow users to proper configure this according to their environment.

See original description
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
assignee: nobody → Fernando Ferraz (fernando-ferraz)
status: New → In Progress
Fernando Ferraz (fernando-ferraz)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.opendev.org/756130
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=c607a82a992ebe63b4ae005746f2b9e8104bb3a0
Submitter: Zuul
Branch: master

commit c607a82a992ebe63b4ae005746f2b9e8104bb3a0
Author: Fernando Ferraz <email address hidden>
Date: Thu Oct 1 11:20:51 2020 -0300

    NetApp SolidFire: Fix clone and request timeout issues

    Users are experiencing timeout issues in certain environments, mostly
    when volumes are too big (ie. multi-terabyte volumes), due to poor
    network performance or upgrade issues that revolve around the SolidFire
    cluster. A viable solution is to make driver timeout values
    configurable in cinder.conf, so users can set these timeouts
    according to their needs.

    This patch adds two timeout settings to the SolidFire driver
    (for cloning operation and globally to all api requests), to
    allow users to set the appropriate timeouts for their environment.

    Closes-Bug: #1898587
    Change-Id: Ie330c76a5db0ea76d4fed5a6ae7b8736dadc8591

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

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/760572

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (stable/victoria)

Reviewed: https://review.opendev.org/760572
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=3b2e7d662b6cca54d13d46161560a497d4ec5bd0
Submitter: Zuul
Branch: stable/victoria

commit 3b2e7d662b6cca54d13d46161560a497d4ec5bd0
Author: Fernando Ferraz <email address hidden>
Date: Thu Oct 1 11:20:51 2020 -0300

    NetApp SolidFire: Fix clone and request timeout issues

    Users are experiencing timeout issues in certain environments, mostly
    when volumes are too big (ie. multi-terabyte volumes), due to poor
    network performance or upgrade issues that revolve around the SolidFire
    cluster. A viable solution is to make driver timeout values
    configurable in cinder.conf, so users can set these timeouts
    according to their needs.

    This patch adds two timeout settings to the SolidFire driver
    (for cloning operation and globally to all api requests), to
    allow users to set the appropriate timeouts for their environment.

    Closes-Bug: #1898587
    Change-Id: Ie330c76a5db0ea76d4fed5a6ae7b8736dadc8591
    (cherry picked from commit c607a82a992ebe63b4ae005746f2b9e8104bb3a0)

tags: added: in-stable-victoria
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 17.0.1

This issue was fixed in the openstack/cinder 17.0.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 18.0.0.0b1

This issue was fixed in the openstack/cinder 18.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 16.3.0

This issue was fixed in the openstack/cinder 16.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 15.5.0

This issue was fixed in the openstack/cinder 15.5.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (stable/queens)

Change abandoned by "Elod Illes <email address hidden>" on branch: stable/queens
Review: https://review.opendev.org/c/openstack/cinder/+/764981
Reason: This branch of the project has been moved to End of Life. In order to be able to delete the branch open patches need to be abandoned.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (stable/rocky)

Change abandoned by "Brian Rosmaita <email address hidden>" on branch: stable/rocky
Review: https://review.opendev.org/c/openstack/cinder/+/764950
Reason: Rocky transitioned to End of Life by change I600914dd08e9 and is accepting no more changes.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (stable/stein)

Change abandoned by "Brian Rosmaita <email address hidden>" on branch: stable/stein
Review: https://review.opendev.org/c/openstack/cinder/+/764942
Reason: Stein transitioned to End of Life by change Icf9a539a7b8b and is accepting no more changes.

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

Other bug subscribers

Remote bug watches

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