** Tags added: iso-testing
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.launchpad.net/bugs/439288
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
Ubuntu-server-bugs@
Testing with a 20091004 ISO containing -0ubuntu13:
Autoregistration failed after CD install/reboot, the registration logs only
show:
ERROR: you need to be on the CLC host and the CLC needs to be running.
Stopping/starting eucalyptus, autoregistration worked.
Trying to run an instance, it worked
I need to reproduce it with todays 20091002 ISO.
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: Dustin Kirkland (kirkland) => Thierry Carrez (ttx)
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.l
I won't have time to spend more time on that this morning.
I validated that this bug does *not* happen in that scenario:
- Install amd64 20090930.2 ISO (with 0ubuntu12)
- manual registration
- upgrade to 0ubuntu13
I also validated that this bug doesn't occus in that scenario:
- Install i386 20090
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: Thierry Carrez (ttx) => Dustin Kirkland (kirkland)
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.launchpad.net/bugs/439288
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I was able to do this with these instructions:
wget
http://eucalyptussoftware.com/downloads/eucalyptus-images/euca-ubuntu-9.04-x86_64.tar.gz
gunzip euca-ubuntu-9.04-x86_64.tar.gz
tar xvf euca-ubuntu-9.04-x86_64.tar
euca-bundle-image -i
euca-ubuntu-9.04-x86_64/kvm-kernel/vmlinuz-2.6.28-11-gen
The lack of networking appears to be a problem in the particular image I
tried (daily UEC build).
When I run bundle and run an image from Eucalyptus, such as:
*
http://eucalyptussoftware.com/downloads/eucalyptus-images/euca-ubuntu-9.04-x86_64.tar.gz
networking comes up just fine!
I'm now runnin
I'm punting this one back over to you, Thierry, as I was able to run
instances (and my day is ending here).
:-Dustin
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: Dustin Kirkland (kirkland) => Thierry Carrez (ttx)
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.launchpad.
Okay, yeah, so my instance runs after a long time:
RESERVATION r-31500705 admin default
INSTANCEi-3BEB06F3 emi-D5871527192.168.0.250 172.19.1.2
running mykey 0 m1.xlarge 2009-09-30T22:37:49.042Z
canyonedge eki-8F0A139Deri-E
Actually, the last part of the previous comment about "never" moving
pending->running might be premature, actually.
Its still working on creating the instance, I think. In the NC, I can
see:
root 17311 17278 3 17:53 ?00:00:16 /bin/dd
if=/var/lib/eucalyptus/instances/admin/i-3BEB06F3
Thierry,
I *definitely* am not reproducing the 127.0.0.1 error. In my nc.log,
I'm seeing:
[Wed Sep 30 17:37:49 2009][008286][EUCAINFO ] from
http://192.168.0.136:8773/services/Walrus/ueckernel/vmlinuz-2.6.31-11-generic.manifest.xml
[Wed Sep 30 17:37:49 2009][008286][EUCAINFO
This is an install from scratch, using CD install. First test was done
with the autoregistration stuff from Dustin. The logs showed the
external IP to be used.
See above, I tried deregister/manual register. It also showed external
IP being used, and also failed. I think there ios something on the
Is it possible that, at some point, a walrus registration was attempted
with 'localhost'? If so, you'll need to deregister walrus:
euca_conf --deregister-walrus
and try registering again with a valid public IP. This error is
implying that the system believes that a registered walrus lives on
12
Some more information.
I did a 20090930.1 CD-based install.
Cluster : no issue. Looking at the registration logs, I remember seeing some
errors, but the final lines all show "success" with the external IP used, so I
figured everything was ok and fixed.
Node: no issue.
Stopped/started eucalyptus o
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.launchpad.net/bugs/439288
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucal
Needs to be reverted to code from ubuntu12 and uploaded as ubuntu14.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: New => Triaged
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta => None
--
1.6~bzr854-0ubuntu13 fails to run instances
https://bugs.launchpad.ne
16 matches
Mail list logo