Why are you looking at OST check-patch job? it has little to do with how OST runs when it is used to check other projects (For example it runs all suits as opposed to just the stable ones, and it does not use or repo protection mecahnisms...). Also that particular patch plays with repo configuration so it is expected to fail on repo issues...

OST is stable ATM for all projects except engine, here are some passing examples:
- http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/3361/
- http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/3362/
- http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/3349/

I think that is strong enough evidence that the issue is in engine code and not in OST/repos/other places people like to point to.