Bug 1899821 - RHVH 4.4.3 anaconda UI proceeds to begin installation without root password provided
Summary: RHVH 4.4.3 anaconda UI proceeds to begin installation without root password p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: redhat-virtualization-host
Version: 4.4.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.5.0-1
: 4.5.0
Assignee: Lev Veyde
QA Contact: cshao
URL:
Whiteboard:
Depends On: 1981807
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-20 06:07 UTC by SATHEESARAN
Modified: 2023-09-15 01:31 UTC (History)
12 users (show)

Fixed In Version: anaconda-33.16.6.6-1.el8 redhat-virtualization-host-4.5.0-202203151206_8.6
Doc Type: Rebase: Bug Fixes Only
Doc Text:
Rebase package(s) to version anaconda-33.16.6.6-1.el8 For highlights and important bug fixes: include UI change for blocking installation if root password is not set.
Clone Of:
: 1981807 (view as bug list)
Environment:
Last Closed: 2022-06-03 13:48:51 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot of anaconda UI (60.97 KB, image/png)
2020-11-20 06:09 UTC, SATHEESARAN
no flags Details
Screenshot of anaconda UI of RHEL 8.3 Server (94.88 KB, image/png)
2020-11-20 06:11 UTC, SATHEESARAN
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:4896 0 None None None 2022-06-03 13:49:10 UTC

Description SATHEESARAN 2020-11-20 06:07:41 UTC
Description of problem:
-----------------------
With RHVH 4.4.3 ( based on RHEL 8.3 ), anaconda UI proceeds to 'Begin Installation', without user providing the password for 'root' user.

In other words, password for 'root' user is not mandatory like the way this is present in RHEL 8.3 Ananconda UI.

Once starting with OS installation, there is no way to create password for 'root' user, but to drop in to maintenance shell during boot and set the password for 'root'

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHVH 4.4.3

How reproducible:
-------------------
Always

Steps to Reproduce:
-------------------
1. Boot the node using RHVH 4.4.3
2. On the anaconda UI, fill all the mandatory inputs like disks and network
3. skip providing password for 'root' and click on 'Begin Installation'

Actual results:
---------------
RHVH 4.4.3 ISO installation proceeds and completes, but no way to SSH in to the node

Expected results:
-----------------
password for 'root' user should be made mandatory, without that 'Begin Installation' button should be grayed out

Comment 1 SATHEESARAN 2020-11-20 06:09:42 UTC
Created attachment 1731156 [details]
Screenshot of anaconda UI

Comment 2 SATHEESARAN 2020-11-20 06:11:07 UTC
Created attachment 1731158 [details]
Screenshot of anaconda UI of RHEL 8.3 Server

Comment 3 Sandro Bonazzola 2020-11-23 08:02:59 UTC
Conditional NAK for design on 4.4.3-2, we need to check with Anaconda team our options here and cannot guarantee we can make it for 4.4.3-2.

Comment 13 Sandro Bonazzola 2022-03-03 16:29:07 UTC
The anaconda package has been fixed, fix included in anaconda-33.16.6.6-1.el8

Comment 19 cshao 2022-03-18 05:05:23 UTC
Test version:
RHVH-4.5-20220315.0-RHVH-x86_64-dvd1.iso

Test result:
'Begin Installation' button is grayed out without provide root password.
So the bug is fixed, change bug status to VERIFIED.

Comment 21 errata-xmlrpc 2022-06-03 13:48:51 UTC
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 (Important: Red Hat Virtualization security, bug fix, and enhancement update [ovirt-4.5.0]), 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/RHSA-2022:4896

Comment 22 Red Hat Bugzilla 2023-09-15 01:31:19 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


Note You need to log in before you can comment on or make changes to this bug.