yahoo-eng-team team mailing list archive

[Peter Nordquist <peter.nordquist@xxxxxxxx>]

Public bug reported:

In the Mitaka Release of Horizon, the Launch Instance NG panels do not
select the 'default' security group and if there is only one network in
a Project it does not default to that network.  In the Launch Instance
Legacy workflow, this defaulted to the 'default' security group and if
you only had one network it defaulted to select that network.  In
Mitaka, the Launch Instance Legacy workflow no longer selects the
'default' security group since it is defaulting to using the string
instead of the id of the 'default' network and this change broke that
[0].  I'm not expecting the Launch Instance Legacy workflow to be fixed,
just documenting that fact since I switched back to that workflow
expecting it to work like the Kilo dashboard.

[0]: https://github.com/openstack/horizon/commit/5562694

** 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/1580357

Title:
  Launch Instance NG does not auto select default security group or
  default to selecting the only network in a Project

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In the Mitaka Release of Horizon, the Launch Instance NG panels do not
  select the 'default' security group and if there is only one network
  in a Project it does not default to that network.  In the Launch
  Instance Legacy workflow, this defaulted to the 'default' security
  group and if you only had one network it defaulted to select that
  network.  In Mitaka, the Launch Instance Legacy workflow no longer
  selects the 'default' security group since it is defaulting to using
  the string instead of the id of the 'default' network and this change
  broke that [0].  I'm not expecting the Launch Instance Legacy workflow
  to be fixed, just documenting that fact since I switched back to that
  workflow expecting it to work like the Kilo dashboard.

  [0]: https://github.com/openstack/horizon/commit/5562694

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