[NEUTRON-40] Floating IP returns 409 (in use) when it isn't in use. See PCAP Created: 19/May/15  Updated: 19/Oct/17  Resolved: 21/May/15

Status: Resolved
Project: neutron
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Keith Burns Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File floatingIP-409message.pcapng     File floatingIPassociate.pcapng    
Issue Links:
Blocks
blocks GBP-44 Neutron External Gateway not function... Resolved
Duplicate
is duplicated by NEUTRON-41 Responding 409 to createFloatingIP Resolved
External issue ID: 3283
Priority: High

 Description   

The issue is the PORT create comes in, grabs the floating IP then the FLOATINGIP API call says "Ah, FP in use... 409"

See attached PCAP.

 Comments   
Comment by Keith Burns [ 19/May/15 ]

Attachment floatingIP-409message.pcapng has been added with description: PCAP of 409

Comment by Keith Burns [ 19/May/15 ]

Ed has supplied patch: https://git.opendaylight.org/gerrit/20743

I have to wait to try and get my devstack environment back from the dead. Seems loads has changed of late, and not for the good.

Comment by Ryan Moats [ 19/May/15 ]

patch merged into stable/lithium and cherry picked to master as https://git.opendaylight.org/gerrit/#/c/20745/

Comment by Keith Burns [ 20/May/15 ]

Fixed.

Comment by Keith Burns [ 20/May/15 ]

Attachment floatingIPassociate.pcapng has been added with description: FloatingIPAssociate-409

Comment by Keith Burns [ 20/May/15 ]

Not fixed for Associate:

Commands:
https://gist.github.com/70378420fee74dbfee27

Comment by Ed Warnicke [ 20/May/15 ]

I believe this is fixed by:

https://git.opendaylight.org/gerrit/20767

Comment by Colin Dixon [ 20/May/15 ]

Keith says that testing the fix (20767) resulted in build errors. There may also be information in today's weekly lithium IRC sync here: https://meetings.opendaylight.org/opendaylight-meeting/2015/weekly_lithium_irc_sync/opendaylight-meeting-weekly_lithium_irc_sync.2015-05-20-14.30.html

It then points to the mailing list thread here:
https://lists.opendaylight.org/pipermail/controller-dev/2015-May/009401.html

The key bit is:

> Class.java in openjdk sources indicates that line 359 is in catch:
>
> } catch (NoSuchMethodException e)

{ > throw new InstantiationException(getName()); > }

>
> Which would seem to indicate that the required constructor is not
> visible. And really – org.opendaylight.neutron.transcriber.Activator
> does not define a no-arg constructor. It got removed in
> I1fe214a7523fd7d0cd361957fcf6b182166ec01a – Ed?
>
> Bye,
> Robert

Comment by Colin Dixon [ 20/May/15 ]

The build issue seems to be resolved by deleting the local copy of the neutron repo and then re-cloning. I don't know what wasn't being appropriately cleaned up, but at least we're unblocked there.

I think Flavio is going to merge the patch for 20767 and we can test to see fi the actual bug is fixed.

Generated at Wed Feb 07 20:25:24 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.