[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release

2017-07-11 Thread Dusty Mabe

dustymabe added a new comment to an issue you are following:
``
> However, as of f26 release, this no longer works. Which is surprising given 
> that f26 alpha did work.

pretty sure "alpha" had this change in it - maybe you updated your kickstart 
then and didn't persist the changes? Or maybe used the interactive install. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/296
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release

2017-07-11 Thread Josh Berkus

The issue: `Cannot install to bare metal using kickstart due to ref name 
problems in f26 release` of project: `atomic-wg` has been assigned to `jberkus` 
by jberkus.

https://pagure.io/atomic-wg/issue/296
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release

2017-07-11 Thread Colin Walters

walters added a new comment to an issue you are following:
``
This is 
https://www.redhat.com/archives/anaconda-devel-list/2017-February/msg0.html 
again.

Changing it to `--url="file:///ostree/repo` should fix it.  
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/296
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release

2017-07-11 Thread Josh Berkus

The issue: `Cannot install to bare metal using kickstart due to ref name 
problems in f26 release` of project: `atomic-wg` has been assigned to 
`dustymabe` by jberkus.

https://pagure.io/atomic-wg/issue/296
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #296: Cannot install to bare metal using kickstart due to ref name problems in f26 release

2017-07-11 Thread Josh Berkus

jberkus reported a new issue against the project: `atomic-wg` that you are 
following:
``
I pave my bare metal cluster using a kickstart similar to the one here: 
http://www.projectatomic.io/blog/2016/10/install-with-kickstart/

However, as of f26 release, this no longer works.  Which is surprising given 
that f26 alpha did work.  The problem is this line in my updated kickstart:

ostreesetup --osname="fedora-atomic" --remote="fedora-atomic" 
--url="file:run/install/repo/content/repo" 
--ref="fedora/26/x86_64/atomic-host" --nogpg

This should pull the ref from the local media (USB key).  However, what I get 
now is "openat: no such file or directory" So somehow the ref is broken in the 
ISO.




``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/296
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org