NetApp: Temporary failure in name resolution

Bug #1971542 reported by Maurice Escher
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Maurice Escher

Bug Description


sometimes I get failed NetApp API calls due to temporary DNS issues - in my case it is related to the underlying kubernetes coredns, which will also be fixed to have less hickups.


Nevertheless the client can also be improved to handle such temporary issues, since it already makes the impression it is doing multiple retries and gave up only after that.
But looking closer, the default max_retries of the requests underlying urllib3 is actually 0.

I think it makes sense to implement some retries on connect and read calls.
I'll propose a fix.


Tags: netapp
tags: added: netapp
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master

Changed in manila:
status: New → In Progress
Changed in manila:
importance: Undecided → Low
assignee: nobody → Maurice Escher (maurice-escher)
milestone: none → zed-3
Changed in manila:
milestone: zed-3 → zed-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Submitter: "Zuul (22348)"
Branch: master

commit d3310b0b387727aee17ff1dfe5679c24f8a7c878
Author: Maurice Escher <email address hidden>
Date: Tue May 3 18:19:25 2022 +0200

    [NetApp] Fix lack of retry HTTP requests

    The driver HTTP requester is not handling connection error with some
    retries for avoiding temporary network failure in name resolution.
    This patch adds a custom `HTTPAdapter` with 5 retries, according to
    urrlib3 documentation [1]. Also, the connection retry will be visible
    in the log [2].


    Closes-Bug: #1971542
    Change-Id: Ic9ff8208f10df9dbed09717d6b218f6293d2338a

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

This issue was fixed in the openstack/manila 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.