jira-python DNS issue

[Guy Matz]

Getting this error from jira-python after running it a lot:

 HTTPSConnectionPool(host='company.jira.com', port=443): Max
        retries exceeded with url:
        /rest/api/2/search?jql=project+%3D+NACRFT+and+status+%3D+%22Pending+Networking+Review%22+and+%22IP%2FPort+Updated%22+%3D+%22No%22+ORDER+BY+updated+DESC&fields=%2Aall&fields=comment&fields=changel
        og&expand=changelog%2Ctransitions.fields&startAt=0&validateQuery=
        True&maxResults=50 (Caused by
        NewConnectionError('<requests.packages.urllib3.connection.Verifie
        dHTTPSConnection object at 0x7f07069ecdd8>: Failed to establish a
        new connection: [Errno -3] Temporary failure in name
        resolution',)) while doing GET https://company.jira.com/rest
        /api/2/search [{'params': {'jql': 'project = NACRFT and status =
        "Pending Networking Review" and "IP/Port Updated" = "No" ORDER BY
        updated DESC', 'fields': ['*all', 'comment', 'changelog'],
        'expand': 'changelog,transitions.fields', 'startAt': 0,
        'validateQuery': True, 'maxResults': 50}, 'headers': {'X-
        Atlassian-Token': 'no-check', 'User-Agent': 'python-
        requests/2.9.1', 'Accept': 'application/json,*.*;q=0.9',
        'Content-Type': 'application/json', 'Cache-Control': 'no-cache',
        'Accept-Encoding': 'gzip, deflate', 'Connection': 'keep-alive'}}]
    [2017-11-24 16:02:51,307: WARNING/Worker-1]
    tasks.query_jira[ee5b2725-a31d-

But it's not temporary.  Any thoughts out there?  Thanks!!

P.S. - jira-python library version is 1.0.7

[somethingblue]

Hi Guy,

• Are you using a proxy and if you bypass the proxy do you get the same behavior if you repeatedly run the jira-python code?
• If you flush the DNS Cache on your computer system do you get the same results?
• If you ping the hostname immediately after the failure what results do you get?

At this point I'm thinking there is some cached data may be incorrect.  Perform the test above and let me know the answers to those questions and we'll go from there.

Cheers,

Branden

[Guy Matz]

Waiting for the problem to crop up again . . .  someone "resolved" the issue by rebooting the server.  This seems to indicate that your DNS cache hypothesis may have some validity, but I'd be very surprised if that were the case.  Will update shortly . . .

[somethingblue]

Hi Guy,

Thanks for the update.  Let me know how it goes.

Thanks again,

Branden