[Bug 1749244] Re: test_session_client_debug_logger DiscoveryFailure: Invalid Response on queens

Fri Oct 19 07:27:39 UTC 2018

We ran into the same issue in our infrastructure. Valuable hint was the
following entry in the debug output of tox: "GET http://no.where/v2.0" -
which resulted in a 200 OK response. On a local system this was not the
case as "no.where" should not resolve to anything and the unit test
actually expects an error instead of a successful connection here.

However, in our case a DNS server was the culprit, which still resolved
the name to an internal address. When executing "dig
http://no.where/v2.0" on the system running the unit tests, we saw a DNS
answer. Removing the DNS resolution for "no.where" solved the issue.

So, maybe check the DNS resolution on your CI systems!

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1749244

Title:
  test_session_client_debug_logger DiscoveryFailure: Invalid Response on
  queens

Status in python-cinderclient:
  Confirmed
Status in python-cinderclient package in Ubuntu:
  Triaged

Bug description:
  'tox -e py27' results in a failure for test_session_client_debug_logger:
  keystoneauth1.exceptions.discovery.DiscoveryFailure: Invalid Response - Bad version data returned: <html><body><script>window.location="http://dnserr...

  Full traceback: https://paste.ubuntu.com/p/gzb9pYN9g7/

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-cinderclient/+bug/1749244/+subscriptions