Associating a floating IP address to a server through Horizon failed

Bug #1599698 reported by xiewj
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Brian Haley

Bug Description

In Mitaka,
Associating a floating IP address to a server through Horizon failed

The error info Horizon retruned is as follows:
"Error: Request Failed: internal server error while processing your request. Neutron server returns request_ids: ['req-5519568b-3717-4907-a8c0-618503a538cc']"
Error: Unable to associate IP address 203.0.112.11.

Associating a floating IP address to a server through the 'nova floating-ip-associate <server> <address>' succeeded.

[root@localhost devstack]# nova list

+--------------------------------------+-----------+--------+------------+-------------+----------------------------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-----------+--------+------------+-------------+----------------------------------------------------------------------------+
| 6b7fb5d6-06b8-4398-9fa2-0e73b97c88d1 | instance1 | ACTIVE | - | Running | network1=2001:db8:80d2:c4d3:f816:3eff:fed6:60f5, 198.51.100.7, 203.0.112.4 |
| 42e45336-33a8-4c7c-87d6-46d40c2a34fb | instance2 | ACTIVE | - | Running | network2=2001:db8:a583:1:f816:3eff:fe3c:3590, 203.0.112.68 |
+--------------------------------------+-----------+--------+------------+-------------+----------------------------------------------------------------------------+
[root@localhost devstack]#

The neutron-server thrown an exception,it seems that the arguments Horizon passed is fewer than needed.
2016-07-06 22:22:24.453 TRACE neutron.api.v2.resource File "/opt/stack/neutron/neutron/db/l3_db.py", line 1021, in _internal_fip_assoc_data
2016-07-06 22:22:24.453 TRACE neutron.api.v2.resource 'therefore cannot be bound.') % data)
2016-07-06 22:22:24.453 TRACE neutron.api.v2.resource TypeError: not enough arguments for format string
The detail info is as follows:

Revision history for this message
Brian Haley (brian-haley) wrote :

I'm not sure if there is also a problem with Horizon, but clearly there's a typo in the message string:

msg = (_('Floating IP %(floatingip_id)s is associated '
         'with non-IPv4 address %s(internal_ip)s and '
         'therefore cannot be bound.') % data)

%s(internal_ip)s is bogus - I'll send a patch

affects: python-neutronclient → neutron
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

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

Changed in neutron:
assignee: nobody → Brian Haley (brian-haley)
status: New → In Progress
Changed in neutron:
importance: Undecided → Medium
tags: added: low-hanging-fruit
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/339008
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=04b197947715690c79d28d0a834348752e187013
Submitter: Jenkins
Branch: master

commit 04b197947715690c79d28d0a834348752e187013
Author: Brian Haley <email address hidden>
Date: Thu Jul 7 09:49:47 2016 -0400

    Fix typo in message string causing server exception

    Trivialfix

    Change-Id: I356a53b62047a189aca6df978e50fbb44e204d16
    Closes-bug: #1599698

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/neutron 9.0.0.0b2

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