On 2013-05-02 9:04, Pádraig Brady wrote:
On 05/02/2013 04:49 PM, Steven Hardy wrote:
Hi,
I've been working through debugging a number of issues with cloud-init
0.7.1 as currently packaged for F18.
The most major problem is that it no longer seems possible to define a user
via the user-defined cloud-config data and have that user get an SSH
authorized_keys correctly installed, when the SSH key comes from the Ec2
datasource. This is a regression from the version shipped in F17 AFAICS,
and it's fixed upstream[1].
There are a number of other F18 related fixes upstream which would be
valuable, including:
- Improved hostname handling (doesn't truncate hostnames containing ".")[2]
- Fedora locale, hostname and tz related fixes[3]
- Fedora systemd, blkid and sysconfig fixes (rev 809)[3]
So I'm proposing a rebase to bzr rev 809, which will include fixes for the
issues above, and probably many more by the looks of the changelogs.
I've created a test package:
http://people.redhat.com/~shardy/cloud-init-test/cloud-init-0.7.2-0.1.bzr809.fc18.noarch.rpm
http://people.redhat.com/~shardy/cloud-init-test/cloud-init-0.7.2-0.1.bzr809.fc18.src.rpm
I'd like to know if this update can go into update-testing for F18 - I've
done some basic testing of the package above, and so far all looks OK.
Thanks!
Steve
[1] https://bugs.launchpad.net/cloud-init/+bug/1100920
[2] https://bugs.launchpad.net/heat/+bug/1164400
[3] http://bazaar.launchpad.net/~gpadgett/cloud-init/ovirt/revision/802
Thanks for all the detail.
That all seems sensible to me.
You've not changed cloud-init-fedora.cfg and just updated the logic
to fix known issues.
I'll apply this to rawhide, f18, f19 in your name later this evening.
Sounds reasonable to me. That's the only issue I found as well.
Thanks for handling the update so quickly, Pádraig. 8^)
--
Garrett Holmstrom
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
