Bug 802241
| Summary: | system halts at first reboot after installation with specific kickstart file | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hongqing Yang <hoyang> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, robatino, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | RejectedBlocker | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-05-29 07:37:25 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: |
|
||||||
This is branched from bug 787461 Please provide a reason why this should be considered a Beta blocker, I don't immediately see that it breaches any criteria. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #2) > Please provide a reason why this should be considered a Beta blocker, I don't > immediately see that it breaches any criteria. > > > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers I think it does not meet the F17 Beta Release Criteria article 6 The installer must be able to use all kickstart delivery methods That criterion is really to do with anaconda's methods for _reading_ kickstart files. It's breached if, say, you specify ks=somethingsomething and then anaconda either explodes or fails to read the kickstart. The case where anaconda correctly reads and attempts to process the kickstart, but something about the actual contents of the kickstart causes the installed system not to boot, is really pretty different. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Please state the exact nature of the problem. Where does the boot stop? Attach a screenshot or a log or something. Discussed at 2012-03-16 blocker review meeting. We agreed that as this seems to be down to the kickstart file itself - or, likely, the package groups specified in it - it does not meet the blocker criteria. We suspect the bug here is that the base-x group is not in fact sufficient to produce a successful X startup. Booting to multi-user.target may well work. We will investigate further. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This is fixed with the current release F17 GA |
Created attachment 569295 [details] kickstart file Description of problem: system halts at first reboot after installation with the kickstart file in the attachment. The kickstart file works well with F16. If the packages are removed from the kickstart file, the system can boot normally. Version-Release number of selected component (if applicable): F17- Beta TC1 How reproducible: Steps to Reproduce: 1. install system with ks file 2. 3. Actual results: Expected results: Additional info: