Use subnet id to allocate floating IP

Bug #1689230 reported by wei.ying
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
wei.ying

Bug Description

In the admin Allocate Floating IP form,the options for the pool select are for a subnet instead of the network, so we should use subnet to allocate floating IP.

wei.ying (wei.yy)
Changed in horizon:
assignee: nobody → wei.ying (wei.yy)
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/463356

wei.ying (wei.yy)
Changed in horizon:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

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

commit ba3ef0efb369a0ef4346779016e09b173a538713
Author: wei.ying <email address hidden>
Date: Mon May 8 23:24:22 2017 +0800

    Use subnet id to allocate floating IP in Admin panel

    In the admin allocate floating IP form, the pool select display
    the subnet cidr info, which should be used subnet id when creating a
    floating IP. This patch fix it.

    Change-Id: I4f12027c90e580824d74b10010bf799515920702
    Closes-Bug: #1689230

Changed in horizon:
status: In Progress → Fix Released
Changed in horizon:
milestone: none → pike-2
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 12.0.0.0b2

This issue was fixed in the openstack/horizon 12.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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