Re: [atomic-devel] 2wk atomic release candidate: 20170213: Possible failure on bare metal

[Josh Berkus <jberkus redhat com>]

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-20170213.0/compose/CloudImages/x86_64/images/
>>>
>>> The ISO image is here:
>>>
>>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170213.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170213.0.iso
>>
>> 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?)

-- 
--
Josh Berkus
Project Atomic
Red Hat OSAS