Elastic IP allocations are not inserted into DB
Bug #891903 reported by
wat
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
New
|
Undecided
|
Unassigned |
Bug Description
Elastic IP allocations after they had been allocated once and released are not retained in DB.
The allocations are gone when clc restarts.
From watching the Java object dump, id(=primaryKey) seems not to be reset to -1 on 2nd allocation.
So it cannot be inserted correctly into DB.
Attached patch is to reset id=-1 on releasing addresses.
system:
Eucalyptus : 2.0.3
Host : CentOS5.5
Installed : binary(
Hypervisor : kvm
VNET_MODE : MANAGED
To post a comment you must log in.
This patch is for lp:eucalyptus/2.0 branch