Description of problem: When installing RHV 4.2.1 environment using engine-setup with answer file, the default provider: 'ovirt-provider-ovn' is not functional: 1. It does not pass connection test 2. it has no password field populated. 3. Tenant is also not populated but required. There is a another bug about it during upgrade (https://bugzilla.redhat.com/show_bug.cgi?id=1532018). If you enter correct password and tenant the provider is still not functional, so OVN is not working at all. Version-Release number of selected component (if applicable): ovirt-provider-ovn-1.2.3-1.el7ev.noarch ovirt-engine-4.2.1-0.2.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Use engine-setup with answer file to install RHV and OVN environment. Actual results: Does not pass connection test. Expected results: ovirt-provider-ovn should pass connection test. Additional info: See attached screenshot.
Created attachment 1378351 [details] artifacts
Mor, who created that answer file? Can you compare it to an auto-generated properly-working one?
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
And could you repeat with logs in DEBUG level?
Dan, 1. The logger is already set on debug, but it doesn't log anything about the failure to test the provider (with valid settings). It just logs the error_PROVIDER_FAILURE 5050 error. 2018-01-08 12:48:50,951+02 ERROR [org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand] (default task-27) [b7e53475-83e9-49a7-9b2b-5277bf38b33f] Command 'org.ovirt.engine.core.bll.provider.TestProviderConnectivityCommand' failed: EngineException: (Failed with error PROVIDER_FAILURE and code 5050) 2. We use this answer file template in Jenkins when we build our environments. It worked before other any issues. Do you know if we made changes to the answer file variables? I will try install new engine and generate one. I will update with results.
I just checked in ovirt-system-tests repository for the answer file that we use in OST, and compared it to the one in Jenkins. The only difference is that in Jenkins we explicitly specify to install OVN using 'OVESETUP_OVN/ovirtProviderOvn=bool:True', but it is the default anyway, so I am not sure it makes any difference.
Update: There were some changes on the Jenkins builder job code which automates the building of the environment, which I didn't knew about, until now. The attached answer file might not be relevant to reproduce the password not populated issue. However, this problem still reproducible if you add new providers on engine.
The failed connection test is already addressed in #1532018. If you can create, import or remove networks on the unmodified provider created by engine-setup this bug might be a duplicate of #1532018 and will be not reproducible in a build containing the fix of #1532018. Can you create, import or remove networks on the unmodified provider or is the bug reproducible in a build containing the fix of #1532018?
I am closing this bug. There was a problem in the Jenkins job. It did not set a value for the 'ovirtProviderOvnPassword' key in the answer file.