Bug 181743
Summary: | interactive ks install won't reboot automatically at the end | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | anaconda | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
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-02-17 19:53:19 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: |
Description
Alexandre Oliva
2006-02-16 04:58:55 UTC
Non-interactive installs do reboot (they even shutdown, etc). Do you remember what the old behavior for this situation is? No, I haven't needed to do interactive ks installs in a long time. It doesn't sound right to not reboot, though. How would you justify that? I'd justify it by saying that since you're in an interactive install, you've had to confirm every other setting by clicking something. For instance, you now have to click on the confirmation screen. Even though the UI has been filled in with the data provided by kickstart, you still have to confirm. It's pretty shaky justification and I don't feel strongly about it either way which is why I'm inclined to just make sure it works the way it used to. I think of `interactive' as `let me make sure it got the ks settings right', rather than `do that and disregard some of the settings such as reboot' :-) If I didn't want it to automatically reboot at the end, I might as well comment out the `reboot' directive. Requiring additional interaction at that point is painfully disruptive, since it requires physical access to the box, potentially a long time after installation started. Since there's an easy way to get a prompt for the reboot if you want (take out the reboot directive), and there isn't any way to enable automated reboot if interactive implies there's going to be a prompt, I vote for interactive to not disregard the reboot directive, even if that is a change in behavior. Does this sounds like reasonable reasoning to you? :-) Yes, that sounds reasonable. |