An invalid attempt to associate an already assigned address will cause the current address to be released
Bug #455563 reported by
Neil Soman
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: Address is not currently unassigned: Address [cluster=
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 |
To post a comment you must log in.
Confirmed as present in 2.0.3.