Cant disassociate floating IP from instance panel when using Quantum

[Jacob Cherkas]

Running commit 599b2c08922390db1161766fe70d38f86dc39428.

Froom Instance panel I can assign a floating IP to any instances but disassociate floating IP returns Info: No floating IPs to disassociate.

Under Access & Security , Floating IPs Tab , I can see that the floating IP is assigned to my instances.

From the Floating IPs Tab I can press the Disassociate Floating IP from the instances with no issue.

We are using Quantum to manage Networks.

Tailing the quantum server log, I dont ever see any request for the tenant when trying to execute the operation from the Instances panel.

[Gabriel Hurley (gabriel-hurley)]

Hmmmm... this is an issue with quantum specifically. For Grizzly I'd recommend turning off the "simple floating IP management" feature. Docs here: http://docs.openstack.org/developer/horizon/topics/settings.html#simple-ip-management

We should get this fixed in H, however.

[Jacob Cherkas (jcherkas)]

Gabriel,

Thanks for the reply.

I think there is some confusion here.

Let me explain.

I can disassociate floating IPs from Instances when using Quantum, just not from the Instances Panel.

If you try to disassociate from the Instances Panel, Horizon says there is no floating IP allocated but if you go to Access & Security Panel you can clearly see that a floating IP is assigned.

From that panel (Access & Security) I can disassociate a floating IP with no problems at all.

Its just broken from the Instances Panel.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/26484
Committed: http://github.com/openstack/horizon/commit/de1940c922b0f5fc965a637a9dcf0734530cb85d
Submitter: Jenkins
Branch: master

commit de1940c922b0f5fc965a637a9dcf0734530cb85d
Author: Roman Podolyaka <email address hidden>
Date: Tue Apr 9 16:28:40 2013 +0300

    Fix floating IP management from instance panel.

    Quantum Floating IP API works with ports ids not instances ones
    (opposite to what Nova Network does). So if we want to associate
    (disassociate) an allocated floating IP to some instance we must
    use the "target_id" (which is a port_id in case of Quantum and an
    instance_id in case of Nova network).

    Fixes bug 1158596.

    Change-Id: Iceba4d8ee74bd58dc1cdbda7668841b0a7eb86f1

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/grizzly
Review: https://review.openstack.org/38648

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/38648
Committed: http://github.com/openstack/horizon/commit/aa77d94d09929009a6c8c10a878c541ca9e85afc
Submitter: Jenkins
Branch: stable/grizzly

commit aa77d94d09929009a6c8c10a878c541ca9e85afc
Author: Roman Podolyaka <email address hidden>
Date: Tue Apr 9 16:28:40 2013 +0300

    Fix floating IP management from instance panel.

    Quantum Floating IP API works with ports ids not instances ones
    (opposite to what Nova Network does). So if we want to associate
    (disassociate) an allocated floating IP to some instance we must
    use the "target_id" (which is a port_id in case of Quantum and an
    instance_id in case of Nova network).

    Fixes bug 1158596.

    Change-Id: Iceba4d8ee74bd58dc1cdbda7668841b0a7eb86f1
    (cherry picked from commit de1940c922b0f5fc965a637a9dcf0734530cb85d)