I've been testing more, now with current lucid images, which have newer
cloud-init.
'ngrep port 8773' on the CLC shows:
T 10.55.55.8:39968 - 10.55.55.2:8773 [AP]
GET /2009-04-04/meta-data/instance-id HTTP/1.1..Accept-Encoding: identity..
Host: 169.254.169.254..Connection:
I noticed that above, 10.55.55.8 is the address of the node controller.
In cases where the correct response is found, that token is the public
IP address of the node. That would explain why the search for a
matching VM's IP would fail.
--
UEC guests sometimes fail on consuming user data
I'm testing with a modified version of 20100427.1 (release) in the data
center. In about 4 out of 50 cases, I see the 200 OK error. Running
ngrep to watch data on the CC, I see things like:
T 172.19.1.42:58975 - 169.254.169.254:80 [AP]
GET /2009-04-04/meta-data/instance-id
more testing has led me to the following:
a.) I cannot reproduce the 200 OK response with empty metadata that we see in
the data center rig on my own hardware. That is still an issue.
b.) It appears that in all my tests the metadata service eventually *does* come
up. On average in my tests
Well, as is often the case, user error added some confusion here.
My system (and possibly kirkland and ttx) have a second dhcp server available
on the network. That dhcp server was responding, and sometimes its response
was being accepted rather than that of the CC.
So, user error causes the
** Tags added: iso-testing
--
UEC guests sometimes fail on consuming user data (metadata service isn't ready)
https://bugs.launchpad.net/bugs/566792
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Assigning to Scott, pending input from the Eucalyptus team
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: (unassigned) = Scott Moser (smoser)
--
UEC guests sometimes fail on consuming user data (metadata service isn't ready)
https://bugs.launchpad.net/bugs/566792
You received this bug
I've recreated this with a ttylinux based image, with modifications to access
metadata service early in boot.
I'm attaching that instance here.
this can be registered with 'uec-register-tarball
ttylinux-11.0-fastboot-amd64-0.07.tar.gz mybucket'
it will also boot in smaller than m1.small (ie,
** Attachment added: console log of tty linux based image showing failure
http://launchpadlibrarian.net/44997795/tty-linux-recreate-console.txt
--
UEC guests sometimes fail on consuming user data (metadata service isn't ready)
https://bugs.launchpad.net/bugs/566792
You received this bug
** Summary changed:
- UEC guests sometimes fail on consuming user data
+ UEC guests sometimes fail on consuming user data (metadata service isn't
ready)
--
UEC guests sometimes fail on consuming user data (metadata service isn't ready)
https://bugs.launchpad.net/bugs/566792
You received this
Attaching logs from Carlos.
** Attachment added: clc-logs.tar.gz
http://launchpadlibrarian.net/44918858/clc-logs.tar.gz
--
UEC guests sometimes fail on consuming user data (metadata service isn't ready)
https://bugs.launchpad.net/bugs/566792
You received this bug notification because you are
11 matches
Mail list logo
