ovirt-engine-dwh and ovirt-engine-setup have some constants duplicated on its codebases. Need to find a way to centralize these constants.
Suggestion from didi: create a new ovirt-engine-dwh-setup-common or similar, with all the duplicated stuff.
Proposing CodeChange, thus QE just sanity.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Simone, IIRC you were for keeping these duplicated. What do you think?
If everything depends on engine_common or if we have no side effects requiring it everywhere we can just move there.
Update on this bug status?
All patches have been merged.
For some reason the status of several patches still 'NEW' but should be 'MERGED'
The projects that changed are:
For testing, please check if all the products are installed correctly and nothing is broken.
*** Bug 1363824 has been marked as a duplicate of this bug. ***
verified in rhevm-220.127.116.11-0.1.el7.noarch
Reopening. I wasn't aware of , which reverts much of the changes for this bug.
We are still affected by it in real life. E.g. patchset 28 of  failed, and to prevent the failure I pushed patchset 30, and also  for a "proper fix". The intent of current bug was that patches such as  would not be needed.
Simone pushed  to fix dev-env without dwh. I understand the reasoning and can accept it as a temporary solution, but imo we need a better one on the long term - e.g. make dwh setup mandatory in dev-env, or somehow patch the engine to not fail if it's missing (no idea how much work this will require, the change between 28 and 30 in  wasn't hard).
Didi, can you fix this?
Now got a report that makes me think current bug is still not solved, bug 1465859.
It seems like one of the patches removed  websocket-proxy's copy of ENGINE_FQDN, and that the engine's copy  wasn't changed to have its attributes.
(The fact that they were different at the time is actually current bug).
Ido should be back in 1 week, Ido please have a look.
Working on it.
Movinf back to assigned as per comment #16
The additional issue that is mentioned on comment 14 is being tracked on .
moving back to 'ON_QA'
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.