The openstack-java-glance-* packages in CentOS have been updated in a way
that is now incompatible with how engine had been using Glance.

This in turn causes any OST run to break ATM, which means no patches are
currently making it past OST and CQ and into the 'tested' and nightly
snapshot repositories.

So far we've only seen this affect 'master' but since the change was made
in CentOS, there is no reason to believe it will not break other version as
well.

A fix to engine to make it compatible with the new package had been posted
here:
https://gerrit.ovirt.org/c/93352/

Additionally, an issue in OST had made this harder to diagnose then it
should have been, and was fixed here:
https://gerrit.ovirt.org/c/93350/

Actions required:

   1. Please avoid merging any unrelated patches until the issue is fixed
   2. If you've merged any patches since Friday morning, please not that
   there were probably removed from the change queue asfailed changes, ad
   willl need to be resubmitted by either merging a newer patch to the
   relevant project, commenting "ci re-merge please" on the latest merged
   patch in Gerrit or resenting the Webhook event from GitHub.
   3. If you can please help with reviewing, merging and back-porting the
   patches above to speed up resolution of this issue.

Here is a list of project for which we've seen patches get dropped over the
weekend

   - ovirt-provider-ovn
   - ovirt-engine
   - ovirt-ansible-vm-infra
   - vdsm

Tracker ticket for this issue:
https://ovirt-jira.atlassian.net/browse/OVIRT-2375


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4C662H7SU2JHP4GPVLAGIIUOJUWTQ3EB/

Reply via email to