← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1391698] Re: Sahara should handle 100 response on row update

 

** Also affects: sahara
   Importance: Undecided
       Status: New

** Tags removed: sahara
** Tags added: dashboard

** Summary changed:

- Sahara should handle 100 response on row update
+ [UI] Sahara should handle 100 response on row update

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

Title:
  [UI] Sahara should handle 100 response on row update

Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Sahara:
  New

Bug description:
  I created cluster and was waiting while it is Active. After some time
  I observed in Sahara logs that cluster is already Active. In Horizon
  it was still in Starting state and didn't update. Here what I see in
  horizon logs:

  [12/Nov/2014 00:07:13] "GET /project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633 HTTP/1.1" 200 1033
  [12/Nov/2014 00:07:15] "GET /project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633 HTTP/1.1" 200 1033
  [12/Nov/2014 00:07:20] "GET /project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633 HTTP/1.1" 100 0

  It looks like horizon stops updating cluster table row after 100
  response. I'm not sure why server responded 100, but this is
  definitely wrong behavior either of server side (must not respond with
  100 or should log why this happened) or client side (100 is a valid
  response and should not be treated as fatal error).

  Error from javascript log:
  Failed to load resource: net::ERR_EMPTY_RESPONSE http://localhost:8080/project/data_processing/clusters/?action=row_update&table=clusters&obj_id=e11d0970-2163-4521-92e3-25671087f633

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


References