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

Bug 1457925

Summary:	engine-setup from answer file does not setup OVN provider (not showing in Engine)
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Mor <mkalfon>
Component:	provider	Assignee:	Dominik Holler <dholler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mor <mkalfon>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	1.0.4	CC:	bugs, danken, mkalfon, myakove, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:25:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1448100
Bug Blocks:

Description Mor 2017-06-01 14:26:41 UTC

Description of problem:
When using engine-setup to install OVN using the default OVN answers in the setup process, OVN is not setup correctly, and the external network provider fails to connect to the provider.

UI error: "Failed to communicate with the external provider, see log for additional details."

provider error: "Unauthorized: Error during SSO authentication unauthorized_client : The client is not authorized to request an authorization. It's required to access the system using FQDN."


Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170531203202.git1bf6667.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Install OVN using engine-setup.
2. Press enter on all OVN related questions.
3. OVN provider should be registered without a password (https://bugzilla.redhat.com/1448100).
4. Set a correct password for the default username (admin).
5. Press "Test" to test the communication.

Actual results:
External network provider is not communicating with OVN provider.

Comment 2 Mor 2017-06-01 14:35:16 UTC

ovirt-provider-ovn version:
ovirt-provider-ovn-1.1-2.20170531131557.git61bec06.el7.centos.noarch

Comment 4 Dominik Holler 2017-06-02 12:32:05 UTC

I can not reproduce this bug using defaults of engine-setup.
What do you mean in the step "OVN provider should be registered without a password (https://bugzilla.redhat.com/1448100)." ?

Comment 5 Mor 2017-06-03 20:12:55 UTC

(In reply to Dominik Holler from comment #4)
> I can not reproduce this bug using defaults of engine-setup.
> What do you mean in the step "OVN provider should be registered without a
> password (https://bugzilla.redhat.com/1448100)." ?

I meant that if you do not enter a password for the default user in engine-setup, it creates a provider without stored password. The BZ mentioned is the bug for the issue.

Comment 6 Dan Kenigsberg 2017-06-04 18:03:55 UTC

Mor, can you update the bug summary to reflect the specific case that is broken? You may raise the priority accordingly.

Comment 7 Mor 2017-06-05 07:34:49 UTC

I tried to run engine-setup with answer file to install OVN on a clean environment. 

I the setting OVESETUP_OVN/ovirtProviderOvn=bool:'True' to answer 'Yes' for the install OVN question.

Is there any difference between running the steps mentioned above manually, or running them with engine-setup answer file that has this setting on?

Comment 10 Mor 2017-06-29 14:44:06 UTC

Verified on: 

ovirt-provider-ovn-1.1-2.20170621093219.git8946da2.el7.centos.noarch
ovirt-engine 4.2.0-0.0.master.20170627181935.git9424f9b.el7.centos

Comment 11 Sandro Bonazzola 2017-12-20 11:25:39 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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