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

Bug 1599271

Summary:	SSO authentication to RHV 4.2 fails with error on CFME side, because OVN provider on RHV side is misconfigured
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Martin Perina <mperina>
Component:	ovirt-provider-ovn	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	alkaplan, cpelland, danken, dholler, gblomqui, hkataria, istein, jfrey, jhardy, jprause, lavenel, mkalfon, mmirecki, mperina, mpovolny, myakove, nsimsolo, obarenbo, ratamir, smallamp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	v2v
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1592834	Environment:
Last Closed:	2018-07-19 06:37:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM	Target Upstream Version:
Embargoed:
Bug Depends On:	1592834
Bug Blocks:

Comment 1 Martin Perina 2018-07-09 11:48:54 UTC

I've just cloned this bug from CFME, becuase there is no error on CFME side. But we need to investigate how is it possible that OVN was improperly configured on RHV side and yet started and make available to communicate with CFME, when the 'client_secret' generation is part of engine-setup, when you enable OVN, so it should always be configured properly.

Comment 2 Martin Perina 2018-07-09 11:52:52 UTC

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

Comment 3 Dan Kenigsberg 2018-07-13 22:49:04 UTC

Nissim, Mor: does this happen on a single badly-upgraded system as https://bugzilla.redhat.com/show_bug.cgi?id=1592834#c11 suggests, or is it a universal problem and a v2v blocker as https://bugzilla.redhat.com/show_bug.cgi?id=1592834#c12 suggests?

Do you have valid workaround?

Comment 4 Mor 2018-07-15 09:34:40 UTC

The workaround was to remove ovirt-provider-ovn, its conf files, and reinstall it.

This is still a bug, but it will be hard to reproduce, unless Nism could elaborate on the changes of engine-setup and ovirt-provider-ovn upgrades along the way.

Nism currently doesn't run V2V as far as I know, so it's not considered V2V blocker.

Comment 5 Dan Kenigsberg 2018-07-15 12:46:08 UTC

Nissim: do you have a reproducer for this?
Would it happen to everyone who is upgrading from 4.1+ovn to 4.2?

If not, I do not think we can fix it.

Comment 7 Dan Kenigsberg 2018-07-19 06:37:19 UTC

Nissim, Meni was not involved in this bug. It was filed by Mor who was using your machine. Mor said in comment 4 that you are the only one able to tell what happened on that host.

In other words, please reopen with reproduction steps when this reoccurs.

Comment 8 Raz Tamir 2018-07-19 08:03:34 UTC

Removing needinfo