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

Bug 1751667

Summary:	RHVM Admin user has sufficient permission to start a cluster upgrade, but insufficient to action it, no error shown.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Anthony Hogbin <ahogbin>
Component:	ovirt-engine-ui-extensions	Assignee:	Sharon Gratch <sgratch>
Status:	CLOSED DUPLICATE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.4	CC:	lleistne, michal.skrivanek, mkalinin, sgratch
Target Milestone:	ovirt-4.4.4
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-20 14:03:57 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 Anthony Hogbin 2019-09-12 11:13:10 UTC

DESCRIPTION OF PROBLEM:
=======================
- User able to start a cluster upgrade, however is unclear as to why it started and then stopped;
- Upgrade flag added and removed - no reason obvious as to what has occurred;
- Permissions issues ONLY logged to engine log.


VERSION/RELEASE NUMBER OF SELECTED COMPONENT:
=============================================
- 4.3

HOW REPRODUCEABLE:
==================

- For users with permissions that allow this - every time;

STEPS TO REPRODUCE:
===================
1. Administration portal as user with insufficient rights to upgrade a specific cluster;
2. Compute > Cluster;
3. Upgrade;

ACTUAL RESULTS:
===============
- Upgrade Flag Set
- Upgrade Flag Unset
- No notification as to why this has happened other than in engine log.


EXPECTED RESULT:
================
Validation before, or notification after:
- A. Not be presented with the option if it is not possible for this user;
- B. Make it clear outside of the event log as to why this has failed.

ADDITIONAL INFORMATION:
=======================

Comment 1 Michal Skrivanek 2019-09-17 10:38:31 UTC

this is kind of blocked on bug 1750426.
We don't plan to do any up front permission checks, only improve the feedback when the operation can't be successfully finished.

Comment 3 Sharon Gratch 2020-06-15 15:50:33 UTC

This doesn't have a design yet. Moving to 4.5 for prioritization.

Comment 5 Sharon Gratch 2020-08-20 14:03:57 UTC

This issue will be implemented as part of BZ 1750426.
Therefore we are closing this bug.

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

Comment 6 Sandro Bonazzola 2020-11-17 13:33:34 UTC

Re-targeting to 4.4.4 being marked as duplicate of bug #1750426 which is targeted to 4.4.4.