Bug 215215
Summary: | kickstart install interactive still shows timezone and rootpw screens. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Timms <dtimms> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED NOTABUG | QA Contact: | |||||
Severity: | low | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-11-13 15:16:31 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
David Timms
2006-11-12 13:56:31 UTC
Created attachment 140989 [details]
kickstart.cfg file that is being used.
You have "interactive" specified in your kickstart file, which means to read the data from your ks file, apply it, and stop at every screen. If you want a fully automated install you need to remove that line from the file. Thanks Chris, I misunderstood the docs to mean use interactive if any user input is needed at all during kickstart. It would be common to always need user input in the partitioning/raid/lvm section, and hence my reason to include it. You are correct in that removing interactive solves the problem; and since I have no partitioning information set, the only screen then shown is partitioning step. Looking at it another way: With interactive set, steps keyboard, language, {is there another screen before partitioning ?} are *not* shown, but partitioning {since I included no partitioning info} and {some/all of} the post partitioning steps are shown, even though there a values set for all screens {except partitioning}. This seems to contradict the interactive dsecription supplied. For the rootpw screen, my kickstart definitely has the pw hash, but * are not shown in the dual pw fields, and clicking next on this screen pops ~"you must enter a root pw" message. So I imagine there is something security special about the pw box that it isn't possible to use the rootpw from kickstart.cfg when interactive is set ? The keyboard and language screens are special. The text mode ones very early on are not shown even in an interactive install because they're provided by an entirely different code base. The graphical ones are not shown unless you boot with the nopass option, even in an interactive install. So yes, they do contradict that description. The root password screen is also special in that I don't really know what to do there if user interaction is required. See bug 181740. Basically if you hit the root password screen in any sort of interactive install, we end up throwing away the password you provided in kickstart. Which docs did you use? Perhaps the interactive description there needs clarification. |