Hi, It's great that this is fixed in precisebut has it been back-
ported to lucid?
There's going to be a lot of lucid instances running for a long time to
come, even after precise is released.
I've built myself a lucid development VM, and tried to build the latest
version of cloud-init from p
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/894279
Title:
cloud-init fails to fetch metadata with OpenSt
This bug was fixed in the package cloud-init - 0.6.3~bzr497-0ubuntu1
---
cloud-init (0.6.3~bzr497-0ubuntu1) precise; urgency=low
* New upstream snapshot.
- cloud-config support for configuring apt-proxy
- selection of local mirror based on presense of 'ubuntu-mirror' dns
@Juerg,
Could you test out the cloud-init at trunk right now and see if it fixes your
problem?
The commit at
http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/488
hopefully has a readable description of hte change.
To build a upstream cloud-init, you can just run:
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/894279
Title:
cloud-init fails to fetch metadata with OpenStack
To manage notifications about this
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/894279
Title:
cloud-init fails to fetch metadata with OpenS
I'll get to this early next week.
but one more comment. The initial poll that is timing out for openstack is just
to check to see if the metadata service is there (ie, "is this EC2?"). Then
immediately after that, cloud-init crawls the metadata service. So, we make 1
call until it succedes , a
I'll mark this confirmed as I think it's agreed there is aproblem, just
not what to do about it.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member o
I agree that Nova needs to be fixed but we need a cloud-init fix for the
current Nova as well. As for running an API server on each compute node,
I don't think that's a viable solution for our environment. We've
modified memcached to cache the metadata requests and that seems to help
make things fa
2 seconds might have been low, I agree, however the following works fine:
$ for s in cnn.com brickies.net slashdot.org espn.com; do
python -c 'import urllib2, sys; req=urllib2.Request(sys.argv[1]); \
resp=urllib2.urlopen(req, timeout=float(sys.argv[2])); resp.read()'
"http://$s"; .1
** Package changed: cloud-utils (Ubuntu) => cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/894279
Title:
cloud-init fails to fetch metadata with OpenStack
To
11 matches
Mail list logo
