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

Bug 1890498

Summary:	Keep Upgrade Cluster dialog consistent with GWT by locating the primary action button to the left of the secondary action button
Product:	[oVirt] ovirt-engine	Reporter:	Ivana Saranova <isaranov>
Component:	ovirt-engine-ui-extensions	Assignee:	Scott Dickerson <sdickers>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.3.7	CC:	bugs, dfodor, sgratch
Target Milestone:	ovirt-4.4.4	Flags:	sgratch: ovirt-4.4? pm-rhel: planning_ack+ sgratch: devel_ack+ sgratch: testing_ack?
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:	2020-11-13 11:01:37 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 Ivana Saranova 2020-10-22 12:03:03 UTC

Description of problem:
Part of the https://bugzilla.redhat.com/show_bug.cgi?id=1870718 that hasn't been fixed in the previous patch - Upgrade cluster dialog. Cancel button should be located on the right.

Version-Release number of selected component (if applicable):
ovirt-engine-ui-extensions-1.2.4-1.el8ev.noarch
ovirt-engine-4.4.3.7-0.22.el8ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Open Cluster upgrade dialogue in AdminPortal
2. Check button location
3.

Actual results:
Cancel button is on the left.

Expected results:
Cancel button is on the right.

Additional info:

Comment 1 Casper (RHV QE bot) 2020-11-13 11:01:37 UTC

This bug has a low overall severity and passed automated regreession suite, it is not going to be further verified by QE. If you believe a special care is required feel free to re-open to ON_QA status

Comment 2 Sandro Bonazzola 2020-12-21 12:38:49 UTC

This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.