RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
It's not possible to enter root password in the Root Password spoke if the spoke was visited previously and the content of the fields was erased.

Version-Release number of selected component (if applicable):
RHEL-8.3.0-20200616.0
anaconda-33.16.3.6-1.el8

How reproducible:
Always

Steps to Reproduce:
1. Start graphical installation.
2. Proceed to the "Root Password" spoke.
3. Enter "a" into the "Root Password" field and delete it (Backspace).
4. Click Done to return to the main hub.
5. Enter the "Root Password" spoke again.
6. Try to set a new password.


Actual results:
Unable to set a new password, because both fields are grayed out .

Expected results:
It's possible to set a new password.

Created attachment 1698847 [details]
screnshot

Created attachment 1698848 [details]
anaconda.log

Created attachment 1698849 [details]
syslog

Vladimir, I've messed with this area recently, so giving just a few pointers. The entry is greyed out because root is locked by setting password to "" in
https://github.com/rhinstaller/anaconda/blob/bc5b7d4088396a96860145af438f32196d669faf/pyanaconda/modules/users/users.py#L335
which makes the entry insensitive in the UI I guess. In Fedora, where the ui (checkbox) for locking root is exposed
it would be possible to make the entry sensitive by unchecking the Lock checkbox I think but in RHEL, we hide it:
https://github.com/rhinstaller/anaconda/blob/bc5b7d4088396a96860145af438f32196d669faf/pyanaconda/ui/gui/spokes/root_password.py#L76
... well, you'll find out and fix up what I've started.

Fix candidate PR: https://github.com/rhinstaller/anaconda/pull/2739

Created attachment 1701407 [details]
Updates image for the Github PR

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4729