yahoo-eng-team team mailing list archive

[OpenStack Infra <1716431@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/508777
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=aec3a33a2231ecdcc023bb534a90d898aad4c3dc
Submitter: Zuul
Branch:    master

commit aec3a33a2231ecdcc023bb534a90d898aad4c3dc
Author: Max Yatsenko <myatsenko@xxxxxxxxxxxx>
Date:   Sun Oct 1 20:14:22 2017 +0300

    Fix displaying pool name for floating ip
    
    It fixes an issue when pool name is not
    displayed for floating ip in a case when any
    floating ip is not associated with an instance.
    
    Change-Id: Ic20ec3709fa7c5313f59a16aa32b975eb004f753
    Closes-Bug: #1716431


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
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:
  pool of FIP is not displayed when FIP is not associated in Floating
  IPs tab

Status in OpenStack Dashboard (Horizon):
  Fix Released

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