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

Bug 2095346

Summary:	cluster upgrade wizard does not handle host name selection correctly
Product:	[oVirt] ovirt-engine	Reporter:	Scott Dickerson <sdickers>
Component:	ovirt-engine-ui-extensions	Assignee:	Scott Dickerson <sdickers>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ivana Saranova <isaranov>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5.0.8	CC:	bugs, mavital, michal.skrivanek, sgratch, usurse
Target Milestone:	ovirt-4.5.1	Flags:	sgratch: ovirt-4.5+ mavital: testing_plan_complete- sgratch: planning_ack? sdickers: devel_ack+ sgratch: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-ui-extensions-1.3.4-1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-27 07:10:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	UX	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Scott Dickerson 2022-06-09 15:28:57 UTC

Description of problem:

When a host is selected in the cluster upgrade wizard, the name of the host should be send to the cluster upgrade ansible role.  Currently, an empty list of host names is always sent.


How reproducible:

Open cluster upgrade wizard for a cluster, select a host and submit the action.  No specific `host_names` will be sent.


Actual results:

The ansible variables will always contain `"host_names":[]`.


Expected results:

The ansible variables should contain ever host name of every selected host in the UI.

Comment 1 Ivana Saranova 2022-06-23 11:48:32 UTC

Steps:
1) Run cluster upgrade and check logs that correct hostnames have been provided

Results:
All selected hosts' names have been sent.

Verified in:
ovirt-engine-ui-extensions-1.3.4-1.el8ev.noarch

Comment 2 Scott Dickerson 2022-06-24 12:16:52 UTC

*** Bug 2100515 has been marked as a duplicate of this bug. ***