Bug 859069

Summary: When doing a minimal install, the root password is not set.
Product: [Fedora] Fedora Reporter: William Brown <william>
Component: anacondaAssignee: David Cantrell <dcantrell>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: g.kaviyarasu, joachim.backes, jonathan, kparal, ljozsa, mbanas, robatino, stephent98, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-24 14:31:19 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:
Bug Depends On:    
Bug Blocks: 752661    

Description William Brown 2012-09-20 13:48:44 UTC
Description of problem:
When a minimal or server install option is selected, the root password is not made a mandatory option to change.

How reproducible:
Always

Steps to Reproduce:
1. Start anaconda
2. Select minimal install
3. Install and reboot
  
Actual results:
You are locked out of your system, since no root password was set. 

Expected results:
You are prompted for the root password. Alternately, steps from "first boot" are run in anaconda to create an alternate user etc.

Comment 1 Chris Lumens 2012-09-20 15:23:52 UTC
The final plan here is that the presence or absence of the firstboot package will make the root password spoke required or not.  However, for now you've just got to know to go into that spoke.  This is already a little bit different post-alpha in that it's moved to the progress bar hub.

Comment 2 Jesse Keating 2012-10-02 17:13:42 UTC
*** Bug 862236 has been marked as a duplicate of this bug. ***

Comment 3 Jesse Keating 2012-10-05 22:31:06 UTC
*** Bug 854982 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2012-10-11 01:05:33 UTC
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.15-1.fc18

Comment 5 Fedora Update System 2012-10-11 02:59:11 UTC
Package anaconda-18.15-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.15-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15903/anaconda-18.15-1.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-10-12 01:07:21 UTC
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18

Comment 7 Fedora Update System 2012-10-17 03:10:25 UTC
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18

Comment 8 Fedora Update System 2012-10-18 02:39:11 UTC
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18

Comment 9 Fedora Update System 2012-10-20 01:35:01 UTC
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

Comment 10 Kamil Páral 2012-10-23 14:17:15 UTC
With Anaconda 18.19, you have to enter the root password dialog now. You can still disable it, but then it's your conscious choice. Closing as fixed.

Comment 11 Ladislav Jozsa 2012-10-24 10:34:55 UTC
Kamil, you're right that is your conscious choice. However anaconda should at least warn user (if not disallow it in specific cases) that having root password disabled might result in unbootable system which is exactly the case of Minimal install and disabled root password.

Comment 12 Ladislav Jozsa 2012-10-24 10:35:56 UTC
Sorry, not unbootable - but unusable.

Comment 13 Kamil Páral 2012-10-24 14:02:19 UTC
(In reply to comment #11)
Warning in certain cases would be nice, no doubt about it. But I think a separate bug would be more appropriate.

Comment 14 Ladislav Jozsa 2012-10-24 14:31:19 UTC
OK, filed bug 869675, closing this one.