Bug 1259506
Summary: | anaconda not parsing kickstart files containing %include | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mark Montague <mark> |
Component: | anaconda | Assignee: | David Shea <dshea> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | anaconda-maint-list, awilliam, bissli82, dracut-maint-list, dshea, g.kaviyarasu, harald, jefflund, jonathan, redhat-bugzilla, robatino, vanmeeuwen+fedora, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | AcceptedFreezeException AcceptedBlocker | ||
Fixed In Version: | 23.19.4-1.fc23 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-16 18:35:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1170820, 1170821 | ||
Attachments: |
Description
Mark Montague
2015-09-02 20:11:17 UTC
Created attachment 1069583 [details]
Kickstart file included by ks-f23-main.cfg
dracut does not handle kickstart files... It's the anaconda part in dracut. Proposed as a Blocker for 23-beta by Fedora user dshea using the blocker tracking app because: Proposing under beta criterion "The installer must be able to use all available kickstart delivery methods. " The kickstart criteria are somewhat vague and we've had 'specify exactly what bits of kickstart functionality are release blocking' on the todo list approximately forever. So I'm a bit wibbly-wobbly on the blockeriness of this, but I'm definitely +1 freeze exception at least. For blocker status, I might see it more as final than beta blocker. Discussed at 2015-09-10 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-09-10/f23-blocker-review.2015-09-10-16.00.log.txt . As the kickstart criteria are still not solidly established this came down to a judgement call. We decided this was most appropriate as a freeze exception for Beta and a blocker for Final: it's not severe enough to block Beta. python-blivet-1.12.4-1.fc23 anaconda-23.19.4-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-15846 anaconda-23.19.4-1.fc23, python-blivet-1.12.4-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update anaconda python-blivet'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15846 anaconda-23.19.4-1.fc23, python-blivet-1.12.4-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. (In reply to awilliam from comment #5) > Discussed at 2015-09-10 blocker review meeting: > https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-09-10/f23- > blocker-review.2015-09-10-16.00.log.txt . As the kickstart criteria are > still not solidly established this came down to a judgement call. We decided > this was most appropriate as a freeze exception for Beta and a blocker for > Final: it's not severe enough to block Beta. I'm hitting the 'localhost dracut-initqueue[xxx]: /lib/anaconda-lib.sh: line 212: /tmp/ks.info: No such file or directory' on F23 Release. Is ks broken on Fedora 23? I'm not seeing anything on Common Bugs about this. The fix for this bug was in F23 Final, so either it didn't work, or you're seeing another bug. Please paste or attach your kickstart (minus any sensitive bits, obviously), and anything that looks useful from the log files in /tmp . Will do so this weekend. FWIW, it would seem 1278260 is a duplicate report from release day, with logs. (or maybe not a duplicate, certainly same failure at the end with the missing ks file... my bad... will get back to this on Sunday .au time) Oh, it's entirely possible you're hitting https://fedoraproject.org/wiki/Common_F23_bugs#kickstart-named-repo . Created attachment 1091481 [details] Console output from virt-install of machine + ks files to install machine (In reply to awilliam from comment #13) > Oh, it's entirely possible you're hitting > https://fedoraproject.org/wiki/Common_F23_bugs#kickstart-named-repo . I've added that updates.img in, still getting the problem. Having a bit more of a poke around in the logs (see attached) I'm now no longer of the belief it's the same cause as the original bug here, however it's the same error out at the end. Along with working out what's causing this, maybe there's a case for a bit more descriptive error than this if it's a catchall idk. Anyways, attached all the things. No sensitive data included. Am actually rather hopeful it's merely something obvious that I've done that I can't see.. but otoh maybe not. Again, apols for noise - but best to get it looked at I guess. Created attachment 1093489 [details]
Our ks file which seems to fail int he same way
I inherited our system from someone far more knowledgeable than I, so I don't have much to add other than "me too". However, I've attached our ks file just in case it helps someone see the problem.
issue still exists and was not fixed or fixed correctly in the GA release. Any KS what soever, with the use of "%include" fails with error: "racut-initqueue[587]: /lib/anaconda-lib.sh: line 212: /tmp/ks.info: No such file or directory" Any way to overcome it? or just use ksappend for now? Please fix it by version 24, it is a major impact for us. (In reply to bissli82 from comment #16) > issue still exists and was not fixed or fixed correctly in the GA release. > Any KS what soever, with the use of "%include" fails with error: > > "racut-initqueue[587]: /lib/anaconda-lib.sh: line 212: /tmp/ks.info: No such > file or directory" > > > Any way to overcome it? or just use ksappend for now? > > Please fix it by version 24, it is a major impact for us. It is fixed in 24. There was a pykickstart update that did not make it into F23. (In reply to David Shea from comment #17) > It is fixed in 24. There was a pykickstart update that did not make it into > F23. Thanks for the info, David. I'll mate a note of testing out early releases to see if I can still break it ;) |