We are going to try to release our next 2WA release this week. Feel free to test out today's build and see if there are any issues! The atomic images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170...

Am 13.02.2017 um 16:32 schrieb Dusty Mabe: > We are going to try to release our next 2WA release this week. > Feel free to test out today's build and see if there are any issues! > > The atomic images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... Tested the Cloud-Base vagrant virtualbox image with the puppet selinux modules acceptance tests (https://github.com/voxpupuli/puppet-selinux). Looks good.

Am 13.02.2017 um 22:43 schrieb Dusty Mabe: > > On 02/13/2017 12:11 PM, Thomas Mueller wrote: >> >> Am 13.02.2017 um 16:32 schrieb Dusty Mabe: >>> We are going to try to release our next 2WA release this week. >>> Feel free to test out today's build and see if there are any issues! >>> >>> The atomic images are here: >>> >>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... >> Tested the Cloud-Base vagrant virtualbox image with the puppet selinux >> modules acceptance tests (https://github.com/voxpupuli/puppet-selinux). >> Looks good. > Thanks Thomas. I believe I have talked with you about this before, but > I do want to reiterate that the cloud base images aren't actually ones > we "release" as part of this process. You can use them but we don't > make any guarantees as far as they are concerned. > > See the following ticket: > https://pagure.io/atomic-wg/issue/138 Unfortunatly it's not released - yes I know. Just wanted to provide feedback that it is working and I'm still interested in getting it released. :-)

On 02/13/2017 07:32 AM, Dusty Mabe wrote: > We are going to try to release our next 2WA release this week. > Feel free to test out today's build and see if there are any issues! > > The atomic images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... I get a failure on this in bare metal install. This may be pilot error, see KS file. Installation is on minnowboard from USB key, using the attached kickstart file. Error message is: Failed to pull from repository: g-io-error-quark: No such Metadata object: {long hex key} Interactive install succeeded.

On 02/14/2017 06:33 AM, Dusty Mabe wrote: > > > On 02/13/2017 10:42 PM, Josh Berkus wrote: >> On 02/13/2017 07:32 AM, Dusty Mabe wrote: >>> We are going to try to release our next 2WA release this week. >>> Feel free to test out today's build and see if there are any issues! >>> >>> The atomic images are here: >>> >>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... >>> >>> The ISO image is here: >>> >>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170... >> >> I get a failure on this in bare metal install. This may be pilot error, >> see KS file. >> >> Installation is on minnowboard from USB key, using the attached >> kickstart file. >> >> Error message is: >> >> Failed to pull from repository: g-io-error-quark: No such Metadata >> object: {long hex key} >> >> >> Interactive install succeeded. >> >> > > I know what the problem is here. I'll see if we can fix it in Lorax > when the ISO is created vs making users change their kickstart files. > What's the issue? Is this something we should notify the users about so that they gradually change files (and update our docs?)