landscape-client blocks boot with no ec2 metadata service
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| landscape-client (Ubuntu) |
Fix Released
|
Low
|
Scott Moser | ||
Bug Description
Binary package hint: landscape-client
When booting a UEC image outside of EC2 or UEC (where there is no metadata service), the sysvinit process is blocked on the 'landscape-client' init script that is running 'landscape-
It can be worked around by setting CLOUD=0 in /etc/default/
$ sudo cat /etc/default/
CLOUD=1
However, its annoying to have to change that.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: landscape-client 11.01-0ubuntu0.
ProcVersionSign
Uname: Linux 2.6.38-5-virtual i686
Architecture: i386
Date: Tue Mar 1 02:39:43 2011
Ec2AMI: ami-4a669523
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: t1.micro
Ec2Kernel: aki-407d9529
Ec2Ramdisk: unavailable
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: landscape-client
Related branches
| Scott Moser (smoser) wrote | #1 |
| Thomas Herve (therve) wrote | #2 |
| Thomas Herve (therve) wrote | #3 |
| Scott Moser (smoser) wrote | #4 |
| Scott Moser (smoser) wrote | #5 |
| Changed in landscape-client (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Fix Released |
| assignee: | nobody → Scott Moser (smoser) |
I would argue that CLOUD=1 means that the metadata service is available. We also have that docstring in our code:
This is necessary because the networking init script on Ubuntu is
asynchronous; the network may not actually be up by the time the
landscape-
Is there another way to know if the network is up or not?