This bug was fixed in the package cloud-init - 0.7.5~bzr950-0ubuntu1
---
cloud-init (0.7.5~bzr950-0ubuntu1) trusty; urgency=medium
* New upstream snapshot.
* support for vendor-data in NoCloud
* fix in is_ipv4 to accept IP addresses with a '0' in them.
* Azure: fix
** 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/1269626
Title:
cloud-init Azure Datasource does not detect new instance
To manage notifications
Submitted MP against cloud-init. Pending MP. I am intending on SRU'ing
this for 12.04 and 13.10. Since 12.10 does not use cloud-init
provisioning, there is no reason for SRU'ing against 12.10.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: Cloud-init log
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+attachment/3949810/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Confirmed that this happening in Saucy too.
$ ssh utlemm...@utl-0115-utl-0115-s1-a1.cloudapp.net
ssh: connect to host utl-0115-utl-0115-s1-A1.cloudapp.net port 22: Connection
refused
ssh: connect to host utl-0115-utl-0115-s1-A1.cloudapp.net port 22: Connection
refused
--
You received this bug
Cloud-init log for above comment
** Attachment added: cloud-init.log
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1269626/+attachment/3949827/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Here is a diff between the SharedConfig.xml, with cloud-init.log as an
attachment
--- waagent.pre/SharedConfig.xml2014-01-15 22:46:09.619537000 +
+++ waagent/SharedConfig.xml2014-01-15 22:54:33.606734299 +
@@ -1,32 +1,32 @@
?xml version=1.0 encoding=utf-8?
SharedConfig
From Saucy instance, here is walinuxagent's /var/lib/waagent/waagent.log
Cloud-init is using ba5ce29e7b4d435f8d70ed5b7c471875 as the instance ID,
but that instance ID is not unique when a machine is captured.
2014/01/12 08:12:30 Configured SSH client probing to keep connections alive.
2014/01/15
Okay, I figured it outwe have a race condition.
What is happening is that the Windows Azure datasource starts
WALinuxAgent. WALinuxAgent normally goes off and fetches a bunch of
files. The datasource normally waits for files to show up from
WALinuxAgent. In the case of a capture, the files
** Branch linked: lp:~utlemming/cloud-init/lp1269626
--
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/1269626
Title:
cloud-init Azure Datasource does not detect new instance
To
10 matches
Mail list logo
