Bug 1752554

Summary: root account not unlocked by initial-setup on aarch64 disk images
Product: [Fedora] Fedora Reporter: Paul Whalen <pwhalen>
Component: initial-setupAssignee: Martin Kolman <mkolman>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: jkonecny, mkolman, rvykydal, v.podzimek+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: initial-setup-0.3.74-1.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-03 00:35:54 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:
Attachments:
Description Flags
journalctl
none
initial-setup-ks.cfg
none
anaconda-ks.cfg none

Description Paul Whalen 2019-09-16 15:43:46 UTC 
Description of problem:
After completing initial-setup the root account remains locked. 

Version-Release number of selected component (if applicable):
initial-setup-0.3.73-1.fc31.aarch64

How reproducible:
Every time with the AArch64 disk images.

Steps to Reproduce:
1. Boot an aarch64 disk image, completing initial-setup including the root password. 
2. Attempt to log in to the root account. 
3. Log fails, root account is still locked. 

Actual results:
[root@localhost ~]# cat /etc/shadow
root:!locked::0:99999:7:::
Comment 1 Paul Whalen 2019-09-16 15:45:57 UTC 
Created attachment 1615557 [details]
journalctl
Comment 2 Paul Whalen 2019-09-16 15:46:42 UTC 
Created attachment 1615558 [details]
initial-setup-ks.cfg
Comment 3 Martin Kolman 2019-09-17 10:36:30 UTC 
Could you also attach /root/anaconda-ks.cfg ? Thanks in advance! :)

That should have the kickstart that Initial Setup reads at first startup (initial-setup-ks.cfg is writen out once Initial Setup is completed) and according to the Journal output there is some sort of weird interaction going on.

Also if this started to fail suddenly & worked before, it could very well be do to changes in this kickstart file, as we have not touched the root password creation code recently.
Comment 4 Paul Whalen 2019-09-17 13:18:24 UTC 
Here is the koji task - https://koji.fedoraproject.org/koji/taskinfo?taskID=37611830

Unfortunately not sure when it broke.
Comment 5 Paul Whalen 2019-09-17 13:18:55 UTC 
Created attachment 1615846 [details]
anaconda-ks.cfg
Comment 6 Martin Kolman 2019-09-17 18:18:11 UTC 
Thanks for the file! I have been able to reproduce the issue locally with the initial kickstart and the bug turns out to be a regression in Initial Setup - caused by s simple typo/mixup. :P

Fix PR: https://github.com/rhinstaller/initial-setup/pull/76
Comment 7 Fedora Update System 2019-09-18 13:28:31 UTC 
FEDORA-2019-f43d17f3c0 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-f43d17f3c0
Comment 8 Fedora Update System 2019-09-19 02:30:07 UTC 
initial-setup-0.3.74-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-f43d17f3c0
Comment 9 Fedora Update System 2019-10-03 00:35:54 UTC 
initial-setup-0.3.74-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.