yahoo-eng-team team mailing list archive

[Adam Tengler <adam.tengler@xxxxxxxxxxx>]

Public bug reported:

Version: 9.1.2 Mitaka

In ;Project > Compute > Access and Security; view in Mitaka dashboard,
we found out that on Floating IPs tab, in the Pool column, you can only
see name of the pool if there are floating IPs already associated with
instances. I believe it is cause by this -
https://github.com/openstack/horizon/blob/mitaka-
eol/openstack_dashboard/dashboards/project/access_and_security/tabs.py#L121
. The for cycle populating pool_name attribute on IP is inside 'if
attached_instance_ids' condition. We expect to see which pool floating
IP came from before the association as it was in Liberty. So the
pool_name attribute should be defined in for cycle outside this if
condition.

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

Title:
  IP pool not displaying under certain conditions in Floating IPs tab

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Version: 9.1.2 Mitaka

  In ;Project > Compute > Access and Security; view in Mitaka dashboard,
  we found out that on Floating IPs tab, in the Pool column, you can
  only see name of the pool if there are floating IPs already associated
  with instances. I believe it is cause by this -
  https://github.com/openstack/horizon/blob/mitaka-
  eol/openstack_dashboard/dashboards/project/access_and_security/tabs.py#L121
  . The for cycle populating pool_name attribute on IP is inside 'if
  attached_instance_ids' condition. We expect to see which pool floating
  IP came from before the association as it was in Liberty. So the
  pool_name attribute should be defined in for cycle outside this if
  condition.

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