An invalid attempt to associate an already assigned address will cause the current address to be released

Bug #455563 reported by Neil Soman on 2009-10-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
Confirmed
Undecided
chris grzegorczyk
2.0
Confirmed
Undecided
Unassigned

Bug Description

Not sure if this is correct behavior.

My instance i-5BF709C8 had an IP A.B.C.D

I (incorrectly) tried to associate an already assigned IP

$ euca-associate-address -i i-5BF709C8 192.168.7.187
Address: Address is not currently unassigned: Address [cluster=mycluster2, instanceAddress=10.77.2.25, instanceId=i-4B1F087E, name=192.168.7.187, pending=false, state=assigned, userId=eucalyptus]

This caused i-5BF709C8 to lose its original public IP A.B.C.D, which now shows up as available.

Related branches

Changed in eucalyptus:
assignee: nobody → chris grzegorczyk (chris-grze)
status: New → Confirmed

Confirmed as present in 2.0.3.

Andy Grimm (agrimm) wrote :

This issue is now being tracked upstream at http://eucalyptus.atlassian.net/browse/EUCA-2665

Please watch that issue for further updates.

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

Other bug subscribers