yahoo-eng-team team mailing list archive

[OpenStack Infra <1617769@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/361754
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=2ac3d510147b51c37e343099d4c477d2d7cdd7a3
Submitter: Jenkins
Branch:    master

commit 2ac3d510147b51c37e343099d4c477d2d7cdd7a3
Author: Paulo Matias <matias@xxxxxxxxx>
Date:   Sun Aug 28 12:33:34 2016 -0300

    Add the new device owner flag for HA router interface
    
    Changeset I89b247bdac3aee1e47ee8a1c9f1cb2c385019a51 introduced a new
    device owner flag for HA router interfaces which was still not included
    in Horizon's ROUTER_INTERFACE_OWNERS.
    
    Change-Id: I2db4218e7351e0017a7a74114be6ac7af803476c
    Related-Bug: #1554519
    Closes-Bug: #1617769


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

Title:
  Floating IPs cannot be associated in a HA router setup

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Regression introduced by https://github.com/openstack/neutron-
  lib/commit/0440878cc61737cf68a2f5780fc8af57845078fd

  When Neutron is deployed to implement a HA router setup, Horizon is
  not capable to list targets for floating IP association. The user
  receives only a "No Ports Available" message and is thus unable to
  associate any floating IP through Horizon.

  This happens because get_reachable_subnets [1] always returns an empty
  set, issue which is caused by the absence of the new device owner flag
  for HA router interface ("network:ha_router_replicated_interface") in
  ROUTER_INTERFACE_OWNERS [2].

  I will send a patch to gerrit in a few minutes.

  --

  Expected result: The user should be able to associate a floating IP to
  an instance using Horizon.

  Actual result: The user cannot associate any floating IP because "Port
  to be associated" only displays "No Ports Available".

  Steps to reproduce:
  * Deploy the environment
  * Create an external network, a project network, and a router between them
  * Launch an instance
  * Allocate a floating IP
  * Try to associate a floating IP to the instance

  Environment:
  * OpenStack-Ansible, master branch
  * Multi-node setup
  * Default neutron setup (ml2.lxb)

  --
  References

  [1]
  https://github.com/openstack/horizon/blob/3bd785274636e9f90d11d28428f479e51403c6d1/openstack_dashboard/api/neutron.py#L449

  [2]
  https://github.com/openstack/horizon/blob/3bd785274636e9f90d11d28428f479e51403c6d1/openstack_dashboard/api/neutron.py#L50

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