Bug 730926
| Summary: | system halts at reboot after install with vnc | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hongqing Yang <hoyang> | ||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | anaconda-maint-list, awilliam, jonathan, kparal, mgracik, robatino, vanmeeuwen+fedora | ||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2011-09-21 10:03:12 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: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 713564 | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Hongqing Yang
2011-08-16 09:23:04 UTC
Created attachment 518444 [details]
screenshot
Created attachment 518445 [details]
anaconda logs
reproduced on f16-alpha-rc5, the it works well with minimal install reproduced on f16-beta-tc2 reproduced on f16-beta-rc1 why was this not proposed as a blocker bug? it seems to be one according to the alpha criteria. Reproduced with F16 Beta RC1 i686. Minimal install works, but default install doesn't boot. Proposing as blocker. "In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account." https://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria Created attachment 523957 [details]
boot messages
kamil: the other criterion to cite is "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces " (Alpha) - the two together make this blocker, I think. Created attachment 523959 [details]
boot messages with systemd debug
adamw: Well, it _completed_ the installation, it just doesn't boot afterwards :-) I wasn't sure whether it covers that or not.
Attaching logs with systemd.log_level=debug. Heavy output warning!
I think this is duplicate of bug #737118 Can you please retest with the latest release? (In reply to comment #11) > I think this is duplicate of bug #737118 I just skimmed through the comments, but this bug seems to be happening also for runlevel 5, not just 3. > Can you please retest with the latest release? Latest release of anaconda? In that case we will probably have to wait for F16 Beta RC2. In the screenshot, one of the last messages is running /usr/bin/setup. That is run only in text-mode. So I suspect it's the same problem. No need for latest anaconda, if what I'm saying is right, latest firstboot is enough, that is firstboot-16.4-1 Do we have some compose ready that would include firstboot-16.4-1? I think you don't need a new compose, you just need a repo with the new firstboot package. But I'm not sure if it is anywhere yet. The status on fedora updates is still pending... yeah, you only need a repo for the installer with firstboot in it. the new firstboot was just pushed to testing, so just installing with updates-testing selected might be enough if your mirror is up to date. otherwise, you can put a side repo up and point anaconda at it. *** Bug 738944 has been marked as a duplicate of this bug. *** I have installed system over VNC using updates-testing including firstboot-16.4-1. The system boots. However, it boots only to runlevel 3 and I had to issue "init 5" to see firstboot and user session afterwards. I think this bug can be closed as fixed and I'll file a separate bug report about the wrong default runlevel. *** This bug has been marked as a duplicate of bug 737118 *** |