Elastic IP allocations are not inserted into DB

Bug #891903 reported by wat
8
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(eucalyptus-2.0.3-centos-x86_64.tar.gz)
Hypervisor : kvm
VNET_MODE : MANAGED

Revision history for this message
wat (ssl-eucalyptus-users) wrote :

This patch is for lp:eucalyptus/2.0 branch

Revision history for this message
Andy Grimm (agrimm) wrote :

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

Please watch that issue for further updates.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.