Description of problem: provider-host value in ovirt-provider-ovn.conf is currently set up as 'localhost' by engine, where it should be FQDN to allow CFME to connect to it remotely. Version-Release number of selected component (if applicable): Version 4.2.0-0.0.master.20171103160151.gitcf446d9.el7.centos ovirt-provider-ovn-1.2-0.20171102153014.git7bfd256.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Use engine-setup to setup OVN component. 2. cat /etc/ovirt-provider-conf.conf | grep provider-host. 3. Try to attach RHV through CFME interface. Actual results: CFME fails to connect to RHV, since 'localhost' is being used. Expected results: CFME should be able to connect remotely using a given FQDN name. Additional info:
Created attachment 1348167 [details] logs
I would not like to ship 4.2.0 without it.
Default setting for 'provider-host' is 'localhost': # cat /etc/ovirt-provider-ovn/ovirt-provider-ovn.conf | grep provider-host provider-host=localhost Tested on: ovirt-provider-ovn-1.2.1-1.el7ev.noarch RHV 4.2.0-0.6.el7.noarch
The setting is not done in the default file (this is not touched by the engine-setup). Please check: /etc/ovirt-provider-ovn/conf.d/10_engine_setup.conf
Found it, thanks. # cat /etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf: # This file is automatically generated by engine-setup. Please do not edit [PROVIDER] provider-host=<FQDN> Verified on: RHV 4.2.0-0.6.el7 ovirt-provider-ovn 1.2.1-1.el7ev.noarch
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.