yahoo-eng-team team mailing list archive

[Paulo Matias <1617769@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: horizon
     Importance: Undecided
     Assignee: Paulo Matias (paulo-matias)
         Status: In Progress

-- 
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):
  In Progress

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