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.
There should be no default, then.
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.
Password is not mandatory. note that we do not ask for it if using default credentials
Verified on 4.2.0-0.0.master.20170612192318.gitf773263.el7.centos
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.