Description of problem: engine-setup - choosing the ovn-ovirt-provider option as 'YES' cause the url and provider type are switched in the database. If choosing the new option ovn-ovirt-provider in the engine-setup, it will cause the url and provider type are switched in the database. engine=# select id, name, url, provider_type from providers; id | name | url | provider_type --------------------------------------+------------------------+------------------------------+----------------------- ceab03af-7220-4d42-8f5c-9b557f5d29af | ovirt-image-repository | http://glance.ovirt.org:9292 | OPENSTACK_IMAGE b98b2826-9f44-491d-b7d5-45a27ce322eb | ovirt-provider-ovn | EXTERNAL_NETWORK | http://localhost:9696 It is causing https://bugzilla.redhat.com/show_bug.cgi?id=1438256 If removing this raw, the system tree and external providers is now loaded again. Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170402072517.gitb0c121a.el7.centos How reproducible: 100% Steps to Reproduce: 1. run engine-setup on latest master and choose to install ovirt-ovn-provider Actual results: the url and provider type are switched in the database
*** Bug 1436963 has been marked as a duplicate of this bug. ***
Hi, it seems that http://gerrit.ovirt.org/74968 haven't solved the problem for me. Reported as bug 1438883. Is it supposed to fixed wrong content of `providers` table or do I need to fix it manually?
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.
The patch will fix new setups, but not fix existing ones. Please do the following to fix your setup: sudo -u postgres psql \connect <YOUR DBNAME> delete from providers where url='EXTERNAL_NETWORK'; \q
*** Bug 1436965 has been marked as a duplicate of this bug. ***
Verified on - 4.2.0-0.0.master.20170528182656.git8a070ae.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.