I like all three, to be honest - put a note in the logs, don't
to bodhi and mark as ABORTED in resultsdb.
From what I've seen thus far, it's not a consistent failure but for
some reason, subsequent runs aren't updating bodhi and the bounceback
to PASS only shows up in resultsdb.
Do you have a link for a Bodhi update where this happened? That sounds like a serious
regression, we should look into it.
Given that, I don't think that we
need to report the result to bodhi if it's a freak occurrence.
The other thing I'd like to do is start utilizing artifacts to store
repodata for at least affected runs. I've not been able to reproduce
the issue and I might get at least some more insight into what's going
wrong if I can get my hands on the generated repodata used during the
That's a good idea. Just watch for the repodata size (the extracted repodata is huge,
so we need to store the compressed version).
I'm going to start working on some patches to grab that data and
assuming there are no objections here, handle "inferior architecture"
errors as follows:
- add note to result with similar wording to what Kamil listed above
- mark result as ABORTED
- make sure that it isn't reported to bodhi
Thanks, no objections. I created a ticket, to keep us all sane:) :