Bug 1169542
Summary: | Lockup after clicking to Proceed using Server Anaconda and network-installation iso | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Leslie Satenstein <lsatenstein> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, lsatenstein, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-12-08 21:12:08 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: |
Description
Leslie Satenstein
2014-12-02 00:08:38 UTC
https://dl.fedoraproject.org/pub/alt/stage/21_RC1/ Source of the ISO's DVD server installation also fails. Problem persists Here is the version used https://dl.fedoraproject.org/pub/alt/stage/21_RC4/ Network install version. Provided name to for root password Matching name did not match clicked done, LOCKUP Never got to test for User Will retry with workstation iso. This is against rc4 issued 2014-12-03 today If in a jam, you may note that I have been testing ever beta, and TC4 (2014-11-21) was clean for me. No ability to enter Root or User passwords when proceed is provided. 310gig standard partition. Root and Home were selected to be xfs, boot as ext4, rest as default settings. Are there any unusual processes running? e2fsck? mkfs.whatever? Are there any logs indicating a kernel panic or GTK or X crash? Please refer to the logs shown. I test with real hardware, no VM Please close and refer to 1170803. Common problem Logs are there *** This bug has been marked as a duplicate of bug 1170803 *** |