yahoo-eng-team team mailing list archive

[Doug Fish <drfish@xxxxxxxxxx>]

Public bug reported:

If network connectivity is lost between Horizon and the other services
it can take quite a while (between 1 minute and "forever") before
Horizon returns with any timeout message.  Each of the multiple API
calls it takes to render a page has to timeout serially before the page
is returned.

I think the fix should involve passing a timeout value to the python
clients.   I've surveyed a few and they support it (I assume they all
do).  In an environment where this may be a problem a service_timeout
value can be configured and passed in to the client.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
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/1415925

Title:
  Horizon doesn't timeout promptly when services can't be reached

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  If network connectivity is lost between Horizon and the other services
  it can take quite a while (between 1 minute and "forever") before
  Horizon returns with any timeout message.  Each of the multiple API
  calls it takes to render a page has to timeout serially before the
  page is returned.

  I think the fix should involve passing a timeout value to the python
  clients.   I've surveyed a few and they support it (I assume they all
  do).  In an environment where this may be a problem a service_timeout
  value can be configured and passed in to the client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1415925/+subscriptions