← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1445276] Re: Instance table Ajax update does not trigger for error instance that is deleting

 

[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]

** Changed in: horizon
       Status: Incomplete => Expired

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

Title:
  Instance table Ajax update does not trigger for error instance that is
  deleting

Status in OpenStack Dashboard (Horizon):
  Expired

Bug description:
  When an instance fails to launch, it would get into this state:

   Status: Error, Task: None

  Then when I terminate it, the page refreshes, and the instance is now
  in this state:

   Status: Error, Task: Deleting

  The instance row is now ".status_down" and no Ajax update is
  triggering for this row, because Ajax update is only triggering for
  "tr.ajax-update.status_unknown". This instance row will therefore not
  be removed unless I refresh the page again (despite it is already
  terminated).

  ----

  Screen shots:

  https://www.dropbox.com/s/xysqgna5aenxe6z/1.png?dl=0

  - An instance falls into error state.

  https://www.dropbox.com/s/g6fqkaekaf5jn6d/2.png?dl=0

  - After delete is requested, tr has class status_down instead of
  status_unknown, therefore no update is triggered for this row. row
  stays "Deleting" despite being deleted.

  ----

  To reproduce:

  1. Get an instance to fail to launch and fall into Error state (see below on how we encounter this).
  2. Terminate the instance, page refreshes by itself.
  3. The instance is now in Status: Error, Task: Deleting

  Expected:

  4. Frontend performs Ajax polling and the row is eventually removed.

  Actual:

  4. Frontend does not perform Ajax polling to update the instance.

  ----

  How our instance fails to launch:

  - Nova network is configured to use VlanManager, there are predetermined number of networks, and each network can only be allocated to one project.
  - Create more projects than there are networks available. (note: each project should have at least one instance launched)
  - Launch an instance on a project that does not have a network, nova would raise a NoMoreNetworks exception, and the instance would fail to launch.
  - Horizon shows the instance to be in Status: Error, Task: None

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


References