When using DVR, port list for floating IP is empty

Bug #1388305 reported by Daniel Gauthier
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Chris Johnson

Bug Description

The port list doesn't get updated correctly when using DVR.

see https://ask.openstack.org/en/question/51634/juno-dvr-associate-floating-ip-reported-no-ports-available/ for detail

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/132383

Changed in horizon:
assignee: nobody → Daniel Gauthier (gaud)
status: New → In Progress
Daniel Gauthier (gaud)
summary: - When using DVR, port list for floating IP is empy
+ When using DVR, port list for floating IP is empty
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/132749

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Daniel Gauthier (<email address hidden>) on branch: master
Review: https://review.openstack.org/132383
Reason: bad commit.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Daniel Gauthier (<email address hidden>) on branch: master
Review: https://review.openstack.org/132749
Reason: I already added a commit in https://review.openstack.org/#/c/132749/ , sorry about that, it's my first time using this system.

Revision history for this message
Julie Pichon (jpichon) wrote :

For reference, duplicate bug 1389177 has a bit more information: this happens when selecting the distributed option, but works when the router is centralised. I'm marking this as Medium severity because I'm not sure how widely used the distributed feature is currently (but we already have 3 people reporting the problem). Either way we'll want to backport this to Juno.

tags: added: neutron
tags: added: juno-backport-potential
Changed in horizon:
importance: Undecided → Medium
Changed in horizon:
assignee: Daniel Gauthier (gaud) → Chris Johnson (wchrisjohnson)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/132383
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=70918159d47db4f74de508d8fd945b2439311163
Submitter: Jenkins
Branch: master

commit 70918159d47db4f74de508d8fd945b2439311163
Author: Daniel Gauthier <email address hidden>
Date: Fri Oct 31 23:46:06 2014 -0400

    List port for distributed router interface

    This patch fixes an issue that occurs when a distributed
    virtual router (DVR) is in use on a network and a user
    attempts to assign a floating IP address to an instance.

    The existing approach assumes that only standard routers,
    not DVR based router(s), are in use on the network. As a
    result, if you attempt to assign a floating IP address,
    there are no candidate ports shown in the select to bind
    the floating IP address to. The dialog that allows you
    to attach a floating IP address will show a message in
    the "Port to be associated" select of "No ports available".

    This patch ensures that if a distributed router exists
    for the network, the appropriate port for that router
    is displayed in the list of ports.

    Change-Id: I2a23389aca02ea8ee2cc8970e2a264d2e8c41dae
    Closes-Bug: 1388305

Changed in horizon:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in horizon:
milestone: none → kilo-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: kilo-2 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.