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

Bug 1809040

Summary:	[CNV&RHV] let the user know that token is not valid anymore
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pavol Brilla <pbrilla>
Component:	ovirt-engine	Assignee:	Piotr Kliczewski <pkliczew>
Status:	CLOSED ERRATA	QA Contact:	Pavol Brilla <pbrilla>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	lleistne, mperina, pelauter, pkliczew
Target Milestone:	ovirt-4.4.1
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	ovirt-engine 4.4.0-26 b5b5c99ca2f	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-04 13:21:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavol Brilla 2020-03-02 10:12:44 UTC

Description of problem:
Connection between CNV and RHV is established by token which expires, once token is expired user has no knowledge about this and need to go to logs to find out.


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


How reproducible:
100%


Actual results:
Operations over CNV cluster are not possible

Expected results:
If token is expired I should know about it from GUI

Comment 7 Pavol Brilla 2020-05-14 11:55:28 UTC

Events are correctly inform user about expired token for provider:

Event message delivered: Failed to call Kubevirt/CNV Provider osv, because the authentication information of the provider is invalid/expired.

Software Version:4.4.0-0.33.master.el8ev

Comment 9 errata-xmlrpc 2020-08-04 13:21:50 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: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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-2020:3247