Don't show IPv6 addresses when selecting port for floating IP

Bug #1703360 reported by Dr. Jens Harbott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Trygve Vea

Bug Description

A floating IP can only be associated with an IPv4 address, trying to use an IPv6 address leads to an error like this:

Error: Bad floatingip request: Cannot process floating IP association with fdb7:6005:3c07:0:f816:3eff:fe94:35d4, since that is not an IPv4 address. Neutron server returns request_ids: ['req-1ffbc2fb-5e84-44ac-990e-62be46801e77']

So the selector should only show the IPv4 addresses of an instance to choose from in the "Associate Floating IP" action.

Tested with current stable/ocata.

Tags: neutron
Revision history for this message
Akihiro Motoki (amotoki) wrote :

The issue exists in the master branch too.

tags: added: neutron
Changed in horizon:
importance: Undecided → Medium
status: New → Triaged
milestone: none → queens-1
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/512399

Changed in horizon:
assignee: nobody → Trygve Vea (trygve-vea-gmail)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

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

commit 9d5be5251f31ce78d76f0715402f6e1510ff41a5
Author: Trygve Vea <email address hidden>
Date: Mon Oct 16 21:58:23 2017 +0200

    Hide IPv6-addresses when assigning floating IP addresses

    A floating IP can only be associated with an IPv4 address, so we should
    not show IPv6 addresses in the list of ports when assigning floating IP
    addresses.

    Change-Id: I7b39a263445204a9efbc8fe113cc79146d9bee8c
    Closes-Bug: #1703360
    Closes-Bug: #1724393

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 13.0.0.0b2

This issue was fixed in the openstack/horizon 13.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.