Don't ask me why I installed the aptitude task group uec on my ubuntu
10.04.2 server edition virtualbox image. I wanted to have a minimal
streamlined ubuntu virtual machine for developing for Heroku cedar stack
which is based on ubuntu 10.04 and ruby1.9.2
My virtualbox host machine is running
Don't ask me why I installed the aptitude task group uec on my ubuntu
10.04.2 server edition virtualbox image. I wanted to have a minimal
streamlined ubuntu virtual machine for developing for Heroku cedar stack
which is based on ubuntu 10.04 and ruby1.9.2
My virtualbox host machine is running
I'm marking this WONT FIX, as I do truly believe it is a platform issue,
not anything that cloud-init could recover from.
** Changed in: cloud-init (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I'm marking this WONT FIX, as I do truly believe it is a platform issue,
not anything that cloud-init could recover from.
** Changed in: cloud-init (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: server-nrs
--
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/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
Ubuntu-server-bugs mailing
** Tags removed: server-nrs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
ubuntu-bugs mailing list
** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-11.04 = None
--
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/745930
Title:
cloud-init timeout waiting for metadata
** Changed in: cloud-init (Ubuntu)
Milestone: ubuntu-11.04 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
** Changed in: cloud-init (Ubuntu)
Milestone: None = ubuntu-11.04
--
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/745930
Title:
cloud-init timeout waiting for metadata
** Changed in: cloud-init (Ubuntu)
Milestone: None = ubuntu-11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
** Tags added: server-nrs
--
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/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
Ubuntu-server-bugs mailing
** Tags added: server-nrs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
ubuntu-bugs mailing list
** Attachment added: console log of timeout
https://bugs.launchpad.net/bugs/745930/+attachment/1957169/+files/console-metadata-timeout.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Tags added: iso-testing
--
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/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
Ubuntu-server-bugs mailing
Scott, Was networking up at that stage; and was it possible to connect
to it externally?
Have you only seen this once?
Thanks.
** Changed in: cloud-init (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
Binary package hint: cloud-init
In testing for natty beta-1, we hit a timeout waiting for the metadata
service.
This would occur when the 'cloud-init' ran, meaning that there was a
network interface up.
+
+ This occurred on m1.large in us-west-1.
I had seen this recently on a lucid instance, that caused a publish failure
from the daily build scripts.
That occurred on a m1.large of:
us-west-1 ami-f5bfefb0 canonical
ebs/ubuntu-lucid-10.04-amd64-server-20110201.1
** Attachment added: console log of lucid instance with no metadata
This only occurred once in todays beta-1 testing. I have seen it on
very rare occasion, as noted above.
I started digging a bit through my build logs. The daily build process
launches an m1.large instance in each region to facilitate populating
EBS root instances. On 2011-03-03, I updated the
In my experience in 2008-2009, just because networking is up on an EC2
instance does not mean that 169.254.169.254 is going to accept
connections and requests for meta-data and user-data. You need to wait
for this to become available. I had code to do this in Ubuntu AMIs I
built back then.
On second glance, cloud-init may actually be retrying the connection and
the problem is that sometimes it takes longer than the current number of
retries.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Well, if you lok at the attached console logs, you can see that cloud-
init is retrying. In lucid, we retried 100 times with a increasing back
off, resulting in 17 minutes or so of trying. The build scripts gave up
after 5 minutes.
In natty (both to reduce the pain if cloud-init was installed
** Attachment added: console log of timeout
https://bugs.launchpad.net/bugs/745930/+attachment/1957169/+files/console-metadata-timeout.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745930
Title:
cloud-init timeout waiting for metadata service on EC2
--
ubuntu-bugs mailing list
Scott, Was networking up at that stage; and was it possible to connect
to it externally?
Have you only seen this once?
Thanks.
** Changed in: cloud-init (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
Binary package hint: cloud-init
In testing for natty beta-1, we hit a timeout waiting for the metadata
service.
This would occur when the 'cloud-init' ran, meaning that there was a
network interface up.
+
+ This occurred on m1.large in us-west-1.
I had seen this recently on a lucid instance, that caused a publish failure
from the daily build scripts.
That occurred on a m1.large of:
us-west-1 ami-f5bfefb0 canonical
ebs/ubuntu-lucid-10.04-amd64-server-20110201.1
** Attachment added: console log of lucid instance with no metadata
This only occurred once in todays beta-1 testing. I have seen it on
very rare occasion, as noted above.
I started digging a bit through my build logs. The daily build process
launches an m1.large instance in each region to facilitate populating
EBS root instances. On 2011-03-03, I updated the
In my experience in 2008-2009, just because networking is up on an EC2
instance does not mean that 169.254.169.254 is going to accept
connections and requests for meta-data and user-data. You need to wait
for this to become available. I had code to do this in Ubuntu AMIs I
built back then.
On second glance, cloud-init may actually be retrying the connection and
the problem is that sometimes it takes longer than the current number of
retries.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, if you lok at the attached console logs, you can see that cloud-
init is retrying. In lucid, we retried 100 times with a increasing back
off, resulting in 17 minutes or so of trying. The build scripts gave up
after 5 minutes.
In natty (both to reduce the pain if cloud-init was installed
30 matches
Mail list logo
