There's a config file change required for cloud-init in order for it at all useful. Specifically, the config file now needs to define default_user, like so:
gecos: EC2 user
groups: [wheel, adm]
sudo: ["ALL=(ALL) NOPASSWD:ALL"]
Veersion 0.7.1-2 has the right config and I've confirmed that it works.
Sorry, QA/rel-eng team. Should have caught this sooner. We kinda need it in the release itself so we can make the EC2 images.
(Alternative I guess would be to roll back to 0.7.0 packages, but there's other bugfixes here.)
cloud-init-0.7.1-2.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cloud-init-0.7.1-2.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
As stated, this violates the following F18 final release criterion :
The release must boot successfully as Xen DomU with releases providing a functional, supported Xen Dom0 and widely used cloud providers utilizing Xen. This does not include any issues limited to the release functioning as Xen Dom0
Discussed at 2012-12-17 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-17/f18final-blocker-review-5.2012-12-17-16.40.log.txt . Accepted as a blocker per criterion cited in comment #3.
cloud-init-0.7.1-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Matthew, can you please verify the issue is really fixed now? Thanks!
The karma on the update that confirms the fix.
" mattdm - 2012-12-14 20:15:35
Examined change (minimal) and tested actual build. Looks good. "
plus two others.