Please ignore my previous email. It turned out the following change disabled all jobs against .gitreview and that is the cause why zuul no longer posts result... https://github.com/openstack/puppet-openstack-integration/commit/1914b7ed1e4... I'll fix the gate asap. On Fri, Apr 2, 2021 at 2:49 PM Takashi Kajinami <tkajinam@redhat.com> wrote:

Hi

I have asked for some help in #openstack-infra but didn't get any solution so far Many people might be now on holidays (enjoy holidays!), so let me send this email so that people involved can find this mail after getting back.

A few days ago Wallaby release of openstack puppet modules were created, and the release bot submitted release patches.

However for some patches zuul doesn't return any CI result(it doesn't put verified score)[1]. I posted +2+A on [2] but it is not merged, because it is not verified by zuul. I tried "recheck" but it didn't solve the problem. [1] https://review.opendev.org/c/openstack/puppet-aodh/+/784213/1 [2] https://review.opendev.org/c/openstack/puppet-cloudkitty/+/784230

Currently we don't have any job triggered for the change with .gitreview and I guess that is why we don't get verified. Actually I see that the same patch for puppet-oslo got verified +1, because tripleo job was unexpectedly triggered for the change in .gitreview [2] https://review.opendev.org/c/openstack/puppet-oslo/+/784302

The easiest solution would be to manually squash these two patches into one. However I remember that we did get verified when we created the last Victoria release, and I suspect some change in infra side which resulted in this situation. So it would be nice if I can ask some insights from infra team about this situation.

Thank you, Takashi Kajinami

-- ---------- Takashi Kajinami Principal Software Maintenance Engineer Customer Experience and Engagement Red Hat email: tkajinam@redhat.com