Description of problem:
With a error checked image, and within SERVER version of anaconda, having chosen xfs as the file format, autocreate partitioning but use xfs for / and home, others as defaults, Anaconda starts and appears to be looping. I can't enter passwords into Anaconda's two fields. CPU=100%
Abnormal operation (two tests)
Once Anaconda starts, the menu for providing password for root and user is presented. But neither responds. The help button does not work either.
I entered the system via control-alt-f1..f6 and saw no activity. I ran top, and it showed anaconda at a steady 100%. With top, I checked memory use, and I had about 2 gigs free. I checked some logs, and they are not growing
I chose all but three of the packages related to workspace and after not being able to detect advancement or activity (network light was flashing at a regular pattern), but nothing else (30minutes waiting)
I wanted to discount a memory problem. This time I selected a minimum set of packages. I wished to prove it was not a memory problem.
Just two questions
Has Anaconda changed to only ask for password after installation is completed?
Anyone else tried the same iso?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Source of the ISO's
DVD server installation also fails.
Here is the version used
Network install version.
Provided name to for root password
Matching name did not match
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 ***