#259 testing cloud-init 0.7.9 in Fedora 25
Closed: Fixed Opened by dustymabe.

If we are able to move from 0.7.8 to 0.7.9 version of cloud-init in Fedora 25 we will be able to add support for another cloud provider. I've been told by @larsks that 0.7.9 fixes a lot of bugs and we should probably want to move to it than stay back. I'm still a bit cautious here so let's give the following images a spin and really hammer cloud-init and make a decision.

https://dustymabe.fedorapeople.org/fedora-25-atomic-host-cloud-init-0.7.9.qcow2

https://dustymabe.fedorapeople.org/fedora-25-cloud-base-cloud-init-0.7.9.qcow2

Since we currently don't release updated cloud base images the testing of that image is kind of "extra" but figured I would throw it out there in the hopes we might find a bug that we might not have otherwise.


Metadata Update from @dustymabe:
- Issue tagged with: host

@kevin @roshi @larsks @jasonbrooks @jberkus @gholms - please test

https://bodhi.fedoraproject.org/updates/FEDORA-2017-b8b79a540c

https://bodhi.fedoraproject.org/updates/FEDORA-2017-b8b79a540c

Ok here is a new image to test. Please download it and give karma to the update!

https://dustymabe.fedorapeople.org/fedora-25-atomic-host-cloud-init-final-test-20170328.qcow2

@dustymabe I just tested the new image. It works for me.

@dustymabe Booted successfully here, too. Sanity checks passing, as well. Karma given.

@dustymabe Did some testing with rpm-ostree and atomic cli, everything looks good. Only minor concern is when I attempted to:

# atomic host upgrade
Signature made Sun Mar 26 21:05:54 2017 using RSA key ID 4089D8F2FDB19C98
Can't check signature: public key not found

error: Commit 6a71adb06bc296c19839e951c38dc0b71ee5d7a82262fef9612f256f0c2a70da: GPG signatures found, but none are in trusted keyring

but:

# cat /etc/ostree/remotes.d/fedora-atomic.conf
[remote "fedora-atomic"]
url=https://kojipkgs.fedoraproject.org/atomic/25/
gpgverify=false

I think I shouldn't be able to upgrade from the test image but the GPG message seems weird. Probably not an issue?

Hey @yzhang - yeah this is a custom image I created and I typo-ed it. Should be gpg-verify=false. You can ignore that issue.

This update has enough karma for stable now. Going to close this issue.

Metadata Update from @dustymabe:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Log in to comment on this ticket.

Metadata