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.
Description of problem:
In order to support a more streamlined registration flow for manual registration (vs. pxe automated registrations) we need to configure the root password on RHEVH boxes so that RHEVM can ssh into each node to set up the public key for future SSH sessions
However, we do not want to tie ourselves to needing 'root' user account indefinitely as we have a requirement to remove the root user usage from RHEVH entirely.
Because of this, we should instead add a Configure RHEVM Admin Password option to the RHEV TUI section of RHEVH and add a rhevm_admin_password kernel commandline argument alongside the rhevm_host and other parameters
Under the covers, setting rhevm_admin_password will of course (for now) set the root password, but eventually this can be migrated to a new user other than root (perhaps call it ... rhevm)
The only issue with this approach is that we do already have a root_password kernel cmdline that is not supported and only intended to be used by Red Hat Support. We need to deal with situations where the user attempts to set both root_password and rhevm_admin_password simultaneously. Perhaps a well defined precedence? Or just documentation saying "Don't do that... for now" until we separate out the registration flow from needing root user access
Perry, please explain the purpose of this. Currently RHEV-H downloads the root ssh public key from RHEV-M.
Why do we need to set the root password on RHEV-H? Is it related to bug 735725?
(In reply to comment #1)
> Why do we need to set the root password on RHEV-H? Is it related to bug 735725?
This is to enable "rhevm will pass to rhevh" part from bug 735725
For RHEL installation flow, RHEV-M requires root credentials, and by default, root is not enabled on RHEV-H.
(In reply to comment #0)
> The only issue with this approach is that we do already have a root_password
> kernel cmdline that is not supported and only intended to be used by Red Hat
> Support.
small correction, boot parameters are rootpw and adminpw
> We need to deal with situations where the user attempts to set both
> root_password and rhevm_admin_password simultaneously. Perhaps a well defined
> precedence?
yes, rhevm_admin_password would trump rootpw which makes sense.
> Or just documentation saying "Don't do that... for now" until we
> separate out the registration flow from needing root user access
RTFM is rarely done, so we'd better have sane default
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHEA-2011-1782.html