[Yahoo-eng-team] [Bug 1333144] Re: Jenkins fails patch verification on: ConnectionError: HTTPConnectionPool(host='public.nova.example.com', port=8774): Max retries exceeded

2015-02-05 Thread Thierry Carrez
** Changed in: horizon Status: Fix Committed = Fix Released ** Changed in: horizon Milestone: None = kilo-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).

[Yahoo-eng-team] [Bug 1333144] Re: Jenkins fails patch verification on: ConnectionError: HTTPConnectionPool(host='public.nova.example.com', port=8774): Max retries exceeded

2014-08-07 Thread Chuck Short
** Changed in: horizon/icehouse Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1333144 Title: Jenkins fails patch

[Yahoo-eng-team] [Bug 1333144] Re: Jenkins fails patch verification on: ConnectionError: HTTPConnectionPool(host='public.nova.example.com', port=8774): Max retries exceeded

2014-07-31 Thread Julie Pichon
Actually the fix isn't necessary for Havana (and we didn't backport the !=1.1.6 requirement restriction either) because these tests are skipped already, due to them not working with Keystone v3. Closing the task.

[Yahoo-eng-team] [Bug 1333144] Re: Jenkins fails patch verification on: ConnectionError: HTTPConnectionPool(host='public.nova.example.com', port=8774): Max retries exceeded

2014-07-28 Thread Julie Pichon
Opening a Havana task as well since this is when the test was added and the django_openstack_auth requirement is open ended, https://github.com/openstack/horizon/blob/stable/havana/requirements.txt#L5 ** Also affects: horizon/havana Importance: Undecided Status: New -- You received

[Yahoo-eng-team] [Bug 1333144] Re: Jenkins fails patch verification on: ConnectionError: HTTPConnectionPool(host='public.nova.example.com', port=8774): Max retries exceeded

2014-06-23 Thread Julie Pichon
The problem appears due to 1.1.6 and bug 1308637. However as far as I can tell that patch is not causing the problem itself but only surfacing an issue that already existed within the Horizon test. At this point when we redirect the user to /auth/logout/ in a unit test the user is not properly