We noted that jenkins CI jobs are not always triggered for gerrit changes. While we are investigating this, I want to remind that you always can trigger / re-trigger check-patch jobs yourself. Just go to to the link , insert your change id and trigger it.
Team Lead - Release Management - RHV DevOps - Red Hat
With these 2 changes the ovirt-log-collector will collect storage domain
metadata from all storage domains of the environment in a more efficient
I'll be away for the next 2 weeks, but reviews are welcome. If there is any
problem with one of these patches, please don't merge any of them as they
require each other.
And if you have extra time, reviews are welcome on this series too =D
Please note that patch was merged.
This patch will prevent(with a detailed ERROR) any attempt to modify an
existing DB upgrade script since this may lead to upgrade problems.
The correct way to change something in the database is a new upgrade script.
In a case that the upgrade script must be changed, this can be forced by
adding a special keyword to your commit header.
Please see  description for details.
If you have any questions, please let me know.
 [ERROR] : Changing an existing upgrade script is dangerous and can
cause upgrade problems,
if you are doing that in purpose and sure that there is no
other way to fix the issue you
are working on, please add the key
'Allow-db-upgrade-script-changes:Yes' to your patch commit message."
I am failing to add a host to oVirt due to the following error:
2018-12-23 11:15:29,482+0200 ERROR otopi.context context._executeMethod:152
Failed to execute stage 'Environment customization': Cannot find a valid
baseurl for repo: ovirt
Does someone encounter this issue?