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.

+++ This bug was initially created as a clone of Bug #591864 +++

Description of problem:
To make it really clear to end users that logging in via ssh/console and using normal bash shell/command line tools is unsupported, we should change the shell for root to put the user directly into the ovirt-config-setup tool.

From there, the user can always still get a bash prompt by using the menu option for getting a bash prompt.  But doing it this way, they have to agree to only go to a bash prompt if they are being instructed to do so by support.

Long term for RHEVH in RHEL6, we're going to do this by using a nicer menuing system.  But for RHEVH5.X we might want to just make this small tweak anyhow.

The only negative here is that since RHEVM uses root ssh access to connect to RHEVH this will be problematic.  But we should probably change RHEVM to use a non-root account to connect to both RHEL and RHEVH hosts anyhow.  Perhaps a 'rhevm' user that has sudo privileges.  This rhevm user and the sudo configuration could be set up as part of the vdsm package install (At least that would work on RHEVH, not sure if there is a chicken/egg problem on RHEL hosts)

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

*** This bug has been marked as a duplicate of bug 591864 ***