Bug 1461698

Summary: engine-setup should test OVN provider connection
Product: [oVirt] ovirt-engine Reporter: Mor <mkalfon>
Component: BLL.NetworkAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED WONTFIX QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.0CC: bugs, danken, ylavi
Target Milestone: ---Flags: sbonazzo: ovirt-4.3-
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: 2018-08-08 07:47:18 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:

Description Mor 2017-06-15 08:36:43 UTC
Description of problem:
When using engine-setup to install OVN, it should test the provider connection and show error in case something went wrong.

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

How reproducible:
100%

Steps to Reproduce:
On a clean environment:

1. Run engine-setup.
2. Choose to install OVN.
3. Choose a non existent user for OVN provider (do not accept the default admin@internal) OR type wrong password for existing user (admin@internal).
3. Accept all other setup default questions.

Actual results:
Provider is registered, but is not functional, and if you test it in the UI it fails.

Expected results:
Engine-setup should test the provider connection during runtime, after installing OVN.

Additional info:

Comment 1 Mor 2017-06-21 07:34:10 UTC
*** Bug 1461699 has been marked as a duplicate of this bug. ***

Comment 2 Dan Kenigsberg 2017-06-21 07:51:10 UTC
We could test the new provider after Engine is up, and add a warning if this fails.

Comment 3 Yaniv Lavi 2018-08-08 07:47:18 UTC
Closing old bugs. Please reopen if still needed.
In any case patches are welcomed.