Cannot mark address as allocating[unallocated.false->allocated.true] when it is assigned.true:

Bug #613832 reported by C de-Avillez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Running one instance every ~60-seconds; after a while we started getting

FinishedVerify: Cannot mark address as allocating[unallocated.false->allocated.true] when it is assigned.true: [Address id=5 name=10.55.55.104 cluster=UEC-TEST1 userId=nobody instanceId=available instanceAddress=0.0.0.0 state=AtomicMarkableReference QUIESCENT= transition=[SplitTransition previous=assigned, transition=allocating, next=assigned, pending=true]]Cannot mark address as allocating[unallocated.false->allocated.true] when it is assigned.true: [Address id=5 name=10.55.55.104 cluster=UEC-TEST1 userId=nobody instanceId=available instanceAddress=0.0.0.0 state=AtomicMarkableReference QUIESCENT= transition=[SplitTransition previous=assigned, transition=allocating, next=assigned, pending=true]]

when trying to start an instance. This error happened 479 times in a total of 1,077 instance starts (then I cancelled the run).

In *all* 479 such errors, the IP address being targeted was 10.55.55.104. This IP was not (visibly) in use.

Full logs are at bzr+ssh://bazaar.launchpad.net/~hggdh2/%2Bjunk/uec-qa/
Pushed up to revision 26.

eucalyptus-cc 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
eucalyptus-cloud 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
eucalyptus-common 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
eucalyptus-gl 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
eucalyptus-java-common 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
eucalyptus-sc 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
eucalyptus-walrus 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed
uec-component-listener 2.0~bzr1218-0ubuntu1 eucalyptus install ok installed

Scott Moser (smoser)
Changed in eucalyptus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
C de-Avillez (hggdh2) wrote :

Had it again on the stress test. Once it happens, it keeps on happening. Upstream seems to have some fixes for IP address allocation, so we will wait for them.

Revision history for this message
Ye Wen (wenye) wrote :

We got this in our long term test too. It looked like an addressing issue that we are aware of. Chris has an fix to be committed. I will update once this is confirmed.

Revision history for this message
Ye Wen (wenye) wrote :

Chris has confirmed. He's merging a fix.

Revision history for this message
chris grzegorczyk (chris-grze) wrote :

Working on setting up regression test and merging the fix now.

Revision history for this message
chris grzegorczyk (chris-grze) wrote :

This appears to be resolved on our end in the following rev. Please see the merge log for details.
------------------------------------------------------------
revno: 1220 [merge]
committer: decker <decker@personal-army>
branch nick: devel
timestamp: Tue 2010-08-10 04:22:52 -0700
message:
  merge: fixes to registration and remote bootstrapping of components & forward port of addressing fixes
------------------------------------------------------------

Revision history for this message
Dave Walker (davewalker) wrote :

Marking fixed release, as it seems to be fixed in Maverick.

Changed in eucalyptus (Ubuntu):
status: New → Fix Released
Revision history for this message
C de-Avillez (hggdh2) wrote :

Indeed, I cannot reproduce it.

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.