Bug 887363 - cloud-init 0.7.1 change prevents creation of ec2-user
Summary: cloud-init 0.7.1 change prevents creation of ec2-user
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cloud-init
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Garrett Holmstrom
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Keywords: Reopened
Depends On:
Blocks: F18Blocker, F18FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2012-12-14 19:53 UTC by Matthew Miller
Modified: 2012-12-20 21:20 UTC (History)
7 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-12-20 21:20:23 UTC


Attachments (Terms of Use)

Description Matthew Miller 2012-12-14 19:53:16 UTC
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:


  default_user:
    name: ec2-user
    lock_passwd: true
    gecos: EC2 user
    groups: [wheel, adm]
    sudo: ["ALL=(ALL) NOPASSWD:ALL"]
    shell: /bin/bash


Veersion 0.7.1-2 has the right config and I've confirmed that it works.

http://koji.fedoraproject.org/koji/buildinfo?buildID=372996

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.)

Comment 1 Fedora Update System 2012-12-14 20:11:33 UTC
cloud-init-0.7.1-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/cloud-init-0.7.1-2.fc18

Comment 2 Fedora Update System 2012-12-14 23:21:25 UTC
Package cloud-init-0.7.1-2.fc18:
* 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:
https://admin.fedoraproject.org/updates/FEDORA-2012-20389/cloud-init-0.7.1-2.fc18
then log in and leave karma (feedback).

Comment 3 Tim Flink 2012-12-17 10:10:39 UTC
As stated, this violates the following F18 final release criterion [1]:

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 

[1] http://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria

Comment 4 Adam Williamson 2012-12-17 18:36:47 UTC
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.

Comment 5 Fedora Update System 2012-12-20 05:31:39 UTC
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.

Comment 6 Kamil Páral 2012-12-20 12:52:55 UTC
Matthew, can you please verify the issue is really fixed now? Thanks!

Comment 7 Adam Williamson 2012-12-20 21:20:23 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.