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
|
Low
|
Maurice Escher |
Bug Description
Hi,
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.
e.g. https:/
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.
BR,
Maurice
tags: | added: netapp |
Changed in manila: | |
importance: | Undecided → Low |
assignee: | nobody → Maurice Escher (maurice-escher) |
milestone: | none → zed-3 |
Changed in manila: | |
milestone: | zed-3 → zed-rc1 |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/c/openstack /manila/ +/840431
Review: https:/