marking this as 'Fix Released'
The natty images from 20100302 and larger do not have the file
/etc/default/landscape .
** Changed in: landscape-client (Ubuntu)
Importance: Undecided = Low
** Changed in: landscape-client (Ubuntu)
Status: New = Fix Released
** Changed in:
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-client init script is invoked.
The easiest fix is to put CLOUD=0 in natty (or keep the default value,
really), as Landscape now supports cloud-init startup and it will
prevent that problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, therve. I had not realized/forgotton that vmbuilder was writing
that template file. I will have it not do so in natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726947
Title:
** Branch linked: lp:vmbuilder/0.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726947
Title:
landscape-client blocks boot with no ec2 metadata service
--
ubuntu-bugs mailing list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726947
Title:
landscape-client blocks boot with no ec2 metadata service
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
