I can confirm on my rig.
Other Eucalyptus users have seen it on other platforms (RedHat/Eucalyptus/Xen),
and also linked it to the 2.6.34 kernel, see:
http://open.eucalyptus.com/forum/decrypting-image-exception
** Changed in: eucalyptus (Ubuntu Maverick)
Status: New = Confirmed
--
For the record, root cause is:
ERROR javax.crypto.BadPaddingException: pad block corrupted
javax.crypto.BadPaddingException: pad block corrupted
at org.bouncycastle.jce.provider.JCEBlockCipher.engineDoFinal(Unknown
Source)
at javax.crypto.Cipher.doFinal(Cipher.java:1708)
Decryption works alright for kernel bundle, but not for the image
bundle:
Decrypting image:
//var/lib/eucalyptus/bukkits/ISOtest-20100616103000/lucid-server-uec-amd64-vmlinuz-virtual-HBfS9Es..tgz
Done decrypting:
Tried with current maverick 2.6.35-3-server, same issue.
Registering the image is sufficient to trigger the above error, no need to try
to run an instance.
--
Instances block in pending state, and don't start
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you
From my testing, the bigger the image, the more chances you have of
hitting that error. If I take the lucid image and gradually truncate it,
it starts working when its size is =430Mb. I also have a 200Mb file
that fails, so its not an absolute size thing.
--
Instances block in pending state, and
I also tested bouncycastle 1.45 and it does fail the same.
--
Instances block in pending state, and don't start
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Tags added: kernel-candidate kernel-core kernel-reviewed
** Tags removed: kernel-needs-review kernel-uncat
--
Instances block in pending state, and don't start
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu)
Milestone: None = maverick-alpha-2
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: New
** Also affects: linux (Ubuntu Maverick)
Importance: High
** Tags added: regression-potential
--
Instances block in pending state, and don't start
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Hi Dave,
Please be sure to confirm this issue exists with the latest development release
of Ubuntu. ISO CD images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please
run the following command from a Terminal
(Applications-Accessories-Terminal).
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-needs-review kernel-uncat
** Tags removed: needs-kernel-logs needs-upstream-testing
--
Instances block in pending state, and don't start
Seems to (oddly) be a kernel regression. Reverting to a Lucid kernel on
Maverick resolves this issue.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Instances block in pending state, and don't start
https://bugs.launchpad.net/bugs/588861
You received this bug
** Description changed:
Maverick Alpha 1
euca-run-instances returns success, and an Instance ID is created. The
Instances remain in pending state, and never start.
+ Still investigating the cause:
- Still investigating the cause, two things i'm looking at are:
-
- axis2c.log ==
-
** Tags added: iso-testing
--
Instances block in pending state, and don't start
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
14 matches
Mail list logo
