Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionParikshit Khedekar
2021-12-18 04:31:54 UTC
Description of problem:
When we do a RHEL 9 install, we need to allow root for ssh based logins by
marking the checkbox. This thing is not recorded to the kickstart generated
for the installation and further it blocks the root account if the kickstart
is used as reference kickstart.
The installation works fine with original install and root login works but
when the resultant kickstart is used for other install the root can't loging
with ssh.
This is common practice administrators follow to have a procedure recorded to
kickstart so will create impact on automated installations and post
installation things.
Version-Release number of selected component (if applicable):
RHEL 9 Beta
How reproducible:
Everytime installing RHEL9 from kickstart recorded from a manual install.
Steps to Reproduce:
1. Install RHEL 9
2. In user section allow ssh based login for root
3. Copy the /root/anaconda-ks.cfg file for another install
4. The another install will not allow root login with ssh
Actual results:
Fails to record kickstart properly.
Expected results:
Shall record the option.
Additional info:
We don't see this to RHEL 8 so probably addition of this feature needs some
work in RHEL 9
There is a workaround via %post script for kickstart installations:
%post
echo "PermitRootLogin yes" > /etc/ssh/sshd_config.d/01-permitrootlogin.conf
%end
(In reply to Jan Stodola from comment #6)
> Talked to Radek, an automated test should be implement as part of the
> feature in kickstart-tests, where the installed system can try to ssh
> root@localhost (currently it's not possible in RHEL-9.0 without changing the
> sshd configuration manually).
Kickstart test: https://github.com/rhinstaller/kickstart-tests/pull/730
Confirmed that root ssh login via ssh can be enabled via kickstart: "rootpw --allow-ssh .."
If the new option is not specified, root login using password via ssh is still disabled, as expected.
Also confirmed that the generated kickstart contains the "--allow-ssh" option if password-based SSH root login is enabled during interactive graphical installation.
The new kickstart option will be documented in bug 2083269.
Marking as Verified:Tested using anaconda-34.25.1.7-1.el9.
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-2022:7977