** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/532682
Title:
instance stays in pending for 1 hour, then to
I had the exact same problem with image decryption at walrus. The kernel
and ramdisk are transfered fine to the nc. After reading this bug
report, I upgraded to Lucid Lynx from Karmic, yesterday. But the same
problem exists.
I am struck on this from 5 days now, pleas tell me if there is any
@nipun , please open a new bug, as this one is fix-released. It really
*as* fix released too, the problem that was solved was due to the
manifest path including the string 'tar' in it.
Please do open a new bug and report your problem.
Ideally, use
1. recreate your failure
2. use 'ubuntu-bug
** Branch linked: lp:~eucalyptus-maintainers/eucalyptus/eucalyptus-devel
--
instance stays in pending for 1 hour, then to terminated
https://bugs.launchpad.net/bugs/532682
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Dustin and Daniel worked on this a bit more on friday and seem to have
at least found a workaround. The database was getting stuck. Per
Dustin, it at least appears that this is not a uec-
publish-[image,tarball] as I had thought it might be.
--
instance stays in pending for 1 hour, then to
Dan-
This is the issue you and I looked at on Friday.
I believe we decided that Eucalyptus was blowing up somewhere during the
image decryption, and then the cloud/database worked itself into a nasty
state.
We restarted eucalyptus several times, and eventually we were able to
register the very
I'm not sure why I'm so lucky, but I hit this more times than not...I'm
almost completely unable to register an image that will boot.
It seems critical to me, as it blocks all usage of the installed UEC.
--
instance stays in pending for 1 hour, then to terminated
revno: 1208
fixes bug(s): https://launchpad.net/bugs/532682
committer: Neil
branch nick: 1.6.2
timestamp: Mon 2010-03-08 14:39:06 -0800
message:
fixes LP: #532682
**
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Confirmed = In Progress
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: Daniel Nurmi (nurmi) = Dustin Kirkland (kirkland)
** Changed in: eucalyptus (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
instance stays in
This bug was fixed in the package eucalyptus - 1.6.2-0ubuntu12
---
eucalyptus (1.6.2-0ubuntu12) lucid; urgency=low
* Cherry-pick merge from upstream 1.6.2, now on revision 1208
- LP: #532682 - fix long, pending instances that go straight to
'terminated'
-- Dustin
** Branch linked: lp:ubuntu/eucalyptus
--
instance stays in pending for 1 hour, then to terminated
https://bugs.launchpad.net/bugs/532682
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs
Looking at the logs:
NC fails to get the DecryptedImage from Walrus:
walrus_request(): writing GET/Get DecryptedImage output to
/var/lib/eucalyptus/instances//admin/i-3DB40784/disk
walrus_request(): wrote 30 bytes in 1 writes
walrus_request(): server responded with HTTP code 408 (timeout)
I'm attaching steps that I did after the lucid-image steps above with a
karmic image.
Note, that the karmic image has a ramdisk. This didn't seem to change
anything, the karmic image fails to boot also.
** Attachment added: karmic steps, showing same issue (done after lucid above)
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
instance stays in pending for 1 hour, then to terminated
** Description changed:
On a fresh install of lucid eucalyptus, I did the following:
A. download lucid 20100303 (http://uec-images.ubuntu.com/lucid/)
B. publish it
-uec-publish-tarball lucid-server-uec-amd64.tar.gz lucid-20100303
+ uec-publish-tarball
I followed the attachd file (karmic steps...) on a fresh install of
Eucalyptus and it recreates the problem. That seems to me to rule out
the ramdiskless scapegoat.
$ euca-describe-images
IMAGE eki-68691AF0
karmic-20100127/karmic-server-uec-amd64-vmlinuz-virtual.manifest.xmladmin
16 matches
Mail list logo
