← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1715066] [NEW] Cannot launch instance with Django Launch Instance form when two or more networks

 

Public bug reported:

When LAUNCH_INSTANCE_LEGACY_ENABLED is set to True and the Django launch
instance form is used, a user cannot launch an instance when there is
multiple networks. I selected network(s) and submitted the form, but the
launch instance workflow was shown again. The selected networks are
reset and all networks are shown in the Available Networks. As a result,
users cannot launch instances with the Django Launch Instance form.

It seems something has changed in Django 1.11.

Previously network ID is shown with a small gray characters but now
"(undefined)" is shown, so it looks like generate_html() JS function
does not work expectedly.

** Affects: horizon
     Importance: High
         Status: New


** Tags: pike-backport-potential

** Tags added: pike-backport-potential

** Changed in: horizon
   Importance: Undecided => High

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

Title:
  Cannot launch instance with Django Launch Instance form when two or
  more networks

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  When LAUNCH_INSTANCE_LEGACY_ENABLED is set to True and the Django
  launch instance form is used, a user cannot launch an instance when
  there is multiple networks. I selected network(s) and submitted the
  form, but the launch instance workflow was shown again. The selected
  networks are reset and all networks are shown in the Available
  Networks. As a result, users cannot launch instances with the Django
  Launch Instance form.

  It seems something has changed in Django 1.11.

  Previously network ID is shown with a small gray characters but now
  "(undefined)" is shown, so it looks like generate_html() JS function
  does not work expectedly.

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


Follow ups