eucalyptus fails to start instances

Bug #813266 reported by C de-Avillez on 2011-07-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
linux (Ubuntu)

Bug Description

Testing 10.04.3. Installed from scratch a CLC/Walrus/CC/SC and a NC (sapodilla and soncoya, respectively). Registered Lucid AMD64 and i386 images, and ran an initial test. All instance starts failed.

Rebooted the systems, and ran a 5-instances test. All instances failed.

Looking at the cloud-error.log, I see a series of errors, including 22:06:12 [WalrusImageManager:connector.VM.0.dispatcher.10] ERROR javax.crypto.BadPaddingException: pad block corrupted.

Full logs are saved at bzr://~hggdh2/%2Bjunk/uec-qa/, revision 66.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: eucalyptus-cc 1.6.2-0ubuntu30.5
ProcVersionSignature: Ubuntu 2.6.32-33.70-server
Uname: Linux 2.6.32-33-server x86_64 CC_NAME="UEC-TEST1"
Architecture: amd64
Date: Tue Jul 19 22:16:42 2011
SourcePackage: eucalyptus

C de-Avillez (hggdh2) wrote :
C de-Avillez (hggdh2) wrote :

Raising to Critical, potential blocker for 10.04.3.

Changed in eucalyptus (Ubuntu):
importance: Undecided → Critical
milestone: none → ubuntu-10.04.3
tags: added: iso-testing
Dave Walker (davewalker) wrote :

This could be a duplicate of kernel bug #588861, which we experienced during the Maverick cycle. Adding a linux (Ubuntu) task incase.


This bug is missing log files that will aid in dianosing the problem. From a terminal window please run:

apport-collect 813266

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Dave Walker (davewalker) wrote :

Confirming that this is infact a duplicate of the kernel bug #588861... Not quite sure what has exposed this, as it would seem Lucid kernel would always have had this issue.

Changed in eucalyptus (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers