Gate jobs failed to start on Workflow+1

At 22:10 UTC on August 12 the VMware NSX CI account left a mass recheck comment on hundreds of open reviews. The comment matched the pattern accepted by the upstream OpenStack CI system and so it removed its existing "Jenkins" account verify vote and reenqueued that change into the check pipeline for testing. Because of the load imposed on our system by the bulk of recheck comments from that account, we disabled it and restarted Zuul, intentionally discarding contents of its check pipeline. This left many changes, including the one in question in this bug, with no existing "Jenkins" account verify vote.

Later, when Ihar Hrachyshka approved the current patchset of this change, it was not considered as suitable for enqueuing into the gate because it lacked an appropriate check verify. It was not until testing was re-triggered through a reverify comment that it got retested, and is now in the check pipeline as intended (hopefully on its way into the gate pipeline once it succeeds there).

The short answer is that this is not a bug, but merely fallout from an unfortunate incident, and to keep in mind that if you're going to approve a change which lacks any verify vote at all from the "Jenkins" and is not already in the check pipeline, you should recheck it to kick off testing. The longer-term answer is that we're reevaluating our current "clean check" implementation and possibly replacing it with other similarly effective but less resource-intensive solutions, so this may cease to be an issue soon.