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

Bug 1448100

Summary: [OVN] - oVirt OVN provider password can't be empty
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Mor <mkalfon>
Severity: high Docs Contact:
Priority: medium    
Version: 4.2.0CC: bugs, mkalfon
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The password for ovirt-provider-ovn during engine-setup can not be empty now. Note that during engine installation, we will first be asked to use default credentials, and if so, the prompt for a password will never show. It will be visible if the provider is installed during an engine-setup update run, or if use of default credentials is not chosen.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 11:30:36 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:    
Bug Blocks: 1457925    

Description Michael Burman 2017-05-04 14:18:18 UTC
Description of problem:
[OVN] - oVirt OVN provider password can't be empty.

If choosing to install the ovirt-provider-ovn packages, the default authentication password is 'empty', but it can't be empty, as engine will not accept it and connection to the provider will fail:

code 403, message Forbidden
May 04 16:55:25 mburman-4-test-rpms.scl.lab.tlv.redhat.com python[26103]: 127.0.0.1 - - [04/May/2017 16:55:25] "GET /v2.0/ HTTP/1.1" 403 -

'Test' will fail as engine not accepting empty password for authentication.

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


Steps to Reproduce:
1. Run engine-setup on master version and choose to install ovirt-provider-ovn
oVirt OVN provider user[admin]: 
oVirt OVN provider password[empty]:

2. Choose default admin and password(empty)
3. Finish engine-setup and go the the webadmin and test the ovn-provider

Actual results:
No connection to the provider, authentication has failed with empty password

Expected results:
User should configure password for authentication when running engine-setup and the default shouldn't be empty.

Comment 1 Dan Kenigsberg 2017-05-06 22:19:34 UTC
There should be no default, then.

Comment 2 Mor 2017-06-05 07:43:27 UTC
During fresh install, we intended to take the password of admin@internal as the default password for ovirt-provider-ovn.

But if too complex, we can avoid this, and force the user to retype the password on upgrade and on fresh install.

Comment 3 Marcin Mirecki 2017-06-09 08:07:54 UTC
Password is not mandatory.
note that we do not ask for it if using default credentials

Comment 4 Mor 2017-06-15 09:10:37 UTC
Verified on 4.2.0-0.0.master.20170612192318.gitf773263.el7.centos

Comment 5 Sandro Bonazzola 2017-12-20 11:30:36 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.