Hi, Thanks to all that helped to resolve the issue. ovirt-engine passed in master CQ [1] and we have a new package in tested [2] so you can now go back to normal merging processes [1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change... [2] https://resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/noarch/ thanks, Dafna On Mon, Sep 17, 2018 at 12:17 PM Dafna Ron <dron@redhat.com> wrote:

Hello to all,

I asked to stop merging last week but it seemed to have been ignored so writing again.

*please stop merging to ovirt-engine master until further notice.*

the project has been failing for the last two weeks on various different regressions. You continue to merge changes which means that you are risking further regressions and making it hard to stabilize the master branch for ovirt-engine.

to make it clear: 1. all changes that were merged since sept. 4th to the master branch exist only in the ovirt-engine master branch (i.e they are not included in your project package). 2. any code merged to master in the past two weeks was most likely not tested by CQ since we exit on first test failure (if your code effects anything after the reported issues ran, they would not be tested). 3. you are putting other projects at risk for regressions since they are tested with a 2 weeks old ovirt-engine packages.

Thanks you. Dafna