QA Apps and Bodhi 2.0

[Tim Flink]

I suspect that most folks here are aware of this by now but Bodhi is
scheduled to be upgraded to 2.0 on 2015-09-19 and we've been trying to
make sure that all QA apps are ready for the upgrade.

From a software perspective, the bits that are most affected are
blockerbugs, libtaskotron and resultsdb.

Since packagers are going to start seeing the rpmlint results in bodhi
now, I suspect that we'll start receiving complaints about the
utility/strictness of that check before long. We should make sure that
we're keeping close eye on devel@ and IRC to respond to any
bugs/suggestions/compaints.

I've outlined summaries of what I know about at the moment below.
Please update this if I've missed something, got something wrong or
some part of this changes.

Tim


Blockerbugs
-----------

Needed some changes in the way that it syncs with bodhi. There is no
way to test these changes before things go live but it shouldn't
explode when bodhi changes so long as it's upgraded at pretty much the
same time.

https://phab.qadevel.cloud.fedoraproject.org/T569


libtaskotron
------------

This has been a bit bigger task than we were hoping. For now, the
absolute essentials work but the bodhi_comment is not currently working
so notifications of taskotron failures to packagers will not work once
bodhi is upgraded.

Not really sure how we're going to handle the notifications stuff. I'm
not crazy about putting any time into the bodhi_comment directive but
because of the lack of notice we had on this change, fedmsg emission
isn't ready and probably won't be ready for at least a week or two.

I suspect that we'll need to take a stab at fixing the bodhi_comment
directive and hope that the effort required there won't be too bad. The
discussion around this will continue as we figure out what to do
about it :-/

https://phab.qadevel.cloud.fedoraproject.org/T558


resultsdb
---------

There has been a fix for HTTP_X_FORWARDED_SCHEME waiting push for a
while now but the bodhi folks requested it again today. I fixed an
issue with the code in 'develop', did a new relese, built it and
updated dev.

Everything seems to be going fine with the new version and not much
changed so I'm not expecting many problems.