Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1701317

Summary:	Cockpit Hosted Engine Deployment fails when "Admin portal Password" is left empty
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Evgeny Slutsky <eslutsky>
Component:	cockpit-ovirt	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED DUPLICATE	QA Contact:	Wei Wang <weiwang>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.8-4	CC:	cshao, dfediuck, huzhao, irosenzw, jikwang, lsvaty, mavital, nlevy, qiyuan, sbonazzo, weiwang, yaniwang, yturgema
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-05 09:54:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Evgeny Slutsky 2019-04-18 15:20:18 UTC

Description of problem:

When deploying hosted engine on RHEL using the cockpit interface,
the portal password field is not populated the Installation wizard let you continue with out any warning.



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


How reproducible:


Steps to Reproduce:
1. install RHEL 7.6
2. install rhvm-appliance using 4.2 subscriptions.
3. start cockpit + enable firewalld
4. enter the web ui: https://<host-fqdn>:9090/
5. open the "Hosted Engine Deployment" wizard
6. on wizard step 1: fill the engine VM fqdn + mac + dhcp - click continue
on wizard step 2: accept the default (Admin Portal Password empty)  - click continue



Actual results:
wizard won't let you progress until the password is filled.

Expected results:
wizard let you progress and the deployment fails on "[ INFO ] TASK [Obtain SSO token using username/password credentials]"
[

Additional info:

Comment 1 Wei Wang 2019-04-19 11:02:13 UTC

Test Version:
[4.2]
rhvh-4.2.8.4-0.20190411.0+1
cockpit-ovirt-dashboard-0.11.39-1.el7ev.noarch
ovirt-hosted-engine-setup-2.2.34-1.el7ev.noarch
ovirt-hosted-engine-ha-2.2.19-1.el7ev.noarch

[4.3]
RHVH-4.3-20190418.4-RHVH-x86_64-dvd1.iso
cockpit-ovirt-dashboard-0.12.8-1.el7ev.noarch
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.7-1.el7ev.noarch

Steps:
1. Clean install RHVH
2. enter the web ui: https://<host-fqdn>:9090/
3. open the "Hosted Engine Deployment" wizard
4. on wizard step 1: fill the engine VM fqdn + mac + dhcp - click continue
   on wizard step 2: accept the default (Admin Portal Password empty)  - click continue

Result:
1. For RHVH 4.2, wizard let you progress and the deployment fails on "[ INFO ] TASK [Obtain SSO token using username/password credentials]"
2. For RHVH 4.3, wizard won't let you progress until the password is filled.

QE can reproduce this bug with RHVH 4.2. 

More infos:
There are other issues occur with RHVH 4.2
1. Passwords, root and admin, and the MAC address can be left empty
2. MAC address isn't validated right - missing last character is valid 
   00:11:22:33:44:5 produces no error
3. all error messages are disappearing when editing one of the fields.
   for example, if we have error messages in both 'engine fqdn' and 'MAC address',
   when the user edits the MAC address field both of the errors disappear instead
of just the error near the MAC address field

Comment 2 Ido Rosenzwig 2019-06-02 08:36:55 UTC

This bug was fixed in 4.3 and on master (4.4). should we backport it to 4.2 as well ?

Comment 3 Sandro Bonazzola 2019-06-03 14:34:33 UTC

(In reply to Ido Rosenzwig from comment #2)
> This bug was fixed in 4.3 and on master (4.4). should we backport it to 4.2
> as well ?

No, not needed. Can you please add references to the patches fixing this bug and move to MODIFIED?

Comment 4 Sandro Bonazzola 2019-06-05 09:54:47 UTC

fix was included in cockpit-ovirt-0.12.7 while fixing bug #1693257

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