yahoo-eng-team team mailing list archive

[Matt Borland <palecrow@xxxxxxxxx>]

Public bug reported:

Consistently, Launch Instance from the Angnular Images panel fails on
first attempt.

This is because magic-search relies on elements being present that
aren't always initialized right away.  It's OK, the lifecycle will catch
up, but at first we need to exclude rendering the magic-search when it's
not ready.

You can recreate this by enabling Angular Images panel:

enabled via:
./openstack_dashboard/enabled/_1051_project_ng_images_panel.py

Go to the panel, then with the JS console open, try to launch an
instance from an image in its item actions.  Notice a) how there are
errors in the console and b) how there is Angular crud on many of the
steps using magic-search.

Apply the fix, and see how (a) and (b) are no longer present.

** Affects: horizon
     Importance: Undecided
         Status: New

** Description changed:

- Consistently, Launch Instance from NG Images fails on first attempt.
+ Consistently, Launch Instance from the Angnular Images panel fails on
+ first attempt.
  
  This is because magic-search relies on elements being present that
  aren't always initialized right away.  It's OK, the lifecycle will catch
  up, but at first we need to exclude rendering the magic-search when it's
  not ready.
+ 
+ You can recreate this by enabling Angular Images panel:
+ 
+ enabled via:
+ ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py
+ 
+ Go to the panel, then with the JS console open, try to launch an
+ instance from an image in its item actions.  Notice a) how there are
+ errors in the console and b) how there is Angular crud on many of the
+ steps using magic-search.

** Description changed:

  Consistently, Launch Instance from the Angnular Images panel fails on
  first attempt.
  
  This is because magic-search relies on elements being present that
  aren't always initialized right away.  It's OK, the lifecycle will catch
  up, but at first we need to exclude rendering the magic-search when it's
  not ready.
  
  You can recreate this by enabling Angular Images panel:
  
  enabled via:
  ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py
  
  Go to the panel, then with the JS console open, try to launch an
  instance from an image in its item actions.  Notice a) how there are
  errors in the console and b) how there is Angular crud on many of the
  steps using magic-search.
+ 
+ Apply the fix, and see how (a) and (b) are no longer present.

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

Title:
  Launch Instance from NG Images fails on first attempt

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Consistently, Launch Instance from the Angnular Images panel fails on
  first attempt.

  This is because magic-search relies on elements being present that
  aren't always initialized right away.  It's OK, the lifecycle will
  catch up, but at first we need to exclude rendering the magic-search
  when it's not ready.

  You can recreate this by enabling Angular Images panel:

  enabled via:
  ./openstack_dashboard/enabled/_1051_project_ng_images_panel.py

  Go to the panel, then with the JS console open, try to launch an
  instance from an image in its item actions.  Notice a) how there are
  errors in the console and b) how there is Angular crud on many of the
  steps using magic-search.

  Apply the fix, and see how (a) and (b) are no longer present.

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