What I do:
1) pxeboot F17 TC1
2) "ks=nfs:myserver.example.com:/path/to/ksfile" specified as boot parameter
3) "nfs --server=myserver.example.com --dir=/path/to/repo" specified in ksfile
What I get:
[ 16.535853] dracut: anaconda fetching kickstart from nfs:nas-id-api.ethz.ch:/ID/api/stud/fs1/quota/ks/studroom/fedora-17-devel-x86_64.ks
[ 16.555547] FS-Cache: Loaded
[ 16.558160] Registering the id_resolver key type
[ 16.558229] FS-Cache: Netfs 'nfs' registered for caching
[ 16.839514] dracut: anaconda mounting NFS repo at nfs:nas-id-api.ethz.ch:/ID/api/stud/fs1/quota/repos/rolling/fedora-17-devel-x86_64-os
[ 16.884325] dracut Warning: no suitable images
[ 17.449063] dracut: anaconda mounting NFS repo at nfs:nas-id-api.ethz.ch:/ID/api/stud/fs1/quota/repos/rolling/fedora-17-devel-x86_64-os
[ 17.474231] dracut Warning: Couldn't mount nfs:nas-id-api.ethz.ch:/ID/api/stud/fs1/quota/repos/rolling/fedora-17-devel-x86_64-os
[ 17.483962] dracut Warning: no suitable images
[ 20.493175] eth0: no IPv6 routers present
[ 37.625335] dracut Warning: Unable to process initqueue
[ 37.625844] dracut Warning: /dev/root does not exist
[ 37.626133] dracut Warning: /dev/root does not exist
After that I'm dropped to a dracut shell, but there doesn't seem to be any useful logs available yet. The NFS share is correctly mounted at /run/install/repo, though. And accessible from there, too.
- I do the very same for F16 (and before that others) without any problem whatsoever.
- ksfile and repo lie on the very same NFS share (in different folders, though)
Proposing as F17Blocker.
Could you boot with 'rd.debug' and, once the shell happens, grab /run/initramfs/init.log and attach it to this bug?
Discussed in the 2012-05-01 blocker bug review meeting. We need more information before deciding on blocker status.
Is the repo that you're using in the kickstart a complete repo or just packages?
Created attachment 581526 [details]
init.log taken with rd.debug set
Will, I hope that's what you needed :)
Tim, what's the difference? Are you asking whether there are repodata or not? Anyway, we set up a cronjob to call reposync to get the repo from a mirror once every 6 hours.
Okay, what Tim asked plus some tidbits that were posted on the test-list over the weekend plus some reading got me to: you need LiveOS/squashfs.img available in the base repo. Added that, issue fixed. Though I'm not really happy with this as it's not automatically fetched with reposync :(
Since this behavior now seems to be expected, I'm going to close this. Sorry for the trouble.
You might want to open a bug for reposync; if it's not fetching everything listed in .treeinfo (and .treeinfo itself!) it's not properly syncing repos.