Just to make sure, I've verified this is fixed in the latest daily of
precise builds. Using the user-data attached above, ssh'd into
instance, and saw the following in 0.6.3-0ubuntu1.4/output.log.
cloud-init 0.6.3-0ubuntu1.4
== sources.list.d ===
total 4
-rw-r--r-- 1 root root 178 Jan 18
** Summary changed:
- [SRU] cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated userdata
+ [SRU] apt_sources broken in 0.6.3-0ubuntu1.3
** Summary changed:
- [SRU] apt_sources broken in 0.6.3-0ubuntu1.3
+ [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression]
** Tags added:
I think this should be fix-committed as it is in proposed.
** Changed in: cloud-init (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I'm attaching a user-data file that I've built to demonstrate this issue, and
that it is resolved.
Simply:
* launch an instance with the provided user-data
* ssh to instance. wait for /home/ubuntu/version/ directory to contain
'cloud-init-output.log', and then reboot
On ssh in, you'll see a
Waiving the waiting period in -proposed since this is a critical
regression.
--
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/1100491
Title:
[SRU] apt_sources broken in
This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.4
---
cloud-init (0.6.3-0ubuntu1.4) precise-proposed; urgency=high
* lp-1100491-fix-broken-add-sources.patch: fix use of
'apt_sources' in cloud-config. (LP: #1100491)
-- Scott Moser smo...@ubuntu.com Wed, 16 Jan