On Mon, 8 Aug 2022 at 13:55, Jeremy Stanley fungi@yuggoth.org wrote:

On 2022-08-08 10:16:08 +0200 (+0200), Pierre Riteau wrote:

...

A patch submitted to python-blazarclient by yoctozepto [1] made me

realise

...

the automatic change of Python jobs from yoga to zed missed various repositories [2], mostly python clients. Is there a reason for this?

At least some of those have simply never merged the changes proposed for them at the start of the cycle:

https://review.opendev.org/q/topic:add-zed-python-jobtemplates+is:open

Of course, I should have checked for this as well. So two out of four blazar repositories (blazar-nova and python-blazarclient) have not received the automatic patch. If it's not clear why, I will raise it at the next cycle if it happens again and we can look at logs.

...

Also, one can easily find projects which are using even older job

templates

...

(xena or earlier).

[...]

Ditto:

https://review.opendev.org/q/topic:add-yoga-python-jobtemplates+is:open https://review.opendev.org/q/topic:add-xena-python-jobtemplates+is:open https://review.opendev.org/q/topic:add-wallaby-python-jobtemplates+is:open https://review.opendev.org/q/topic:add-victoria-python-jobtemplates+is:open

I wasn't implying here that automatic patches had been missed, but just pointing out that some projects are trailing behind.

---- On Mon, 08 Aug 2022 18:37:32 +0530 Jeremy Stanley wrote ---

On 2022-08-08 14:50:30 +0200 (+0200), Pierre Riteau wrote: [...]

...

two out of four blazar repositories (blazar-nova and python-blazarclient) have not received the automatic patch. If it's not clear why, I will raise it at the next cycle if it happens again and we can look at logs.

[...]

Agreed, we're discussing it currently in #openstack-release to see if we can understand what happened. Normally those changes are auto-proposed during branch creation, so those projects should have received proposals the moment the release requests to create stable/yoga branches in them merged. There is no indication those changes ever got proposed, and it's been too long now for us to still have CI logs from that timeframe, so we're having to do a bit of theorizing.

In contrast, I can see that python-blazarclient got a similar change proposed to move to the yoga template when stable/xena was created, so that would seem to point to being a more recent issue.

There were other cases also where template update have been missed or not corrct (for example independent release repo). That is why in Zed PTG, we agreed to remove these release specific template and auto generated patches to update the template name. From this cycle onwards, we will be doing these python version change in generic template at single place and do not need to update the python testing template name in every release.

-gmann

-- Jeremy Stanley

---- On Mon, 08 Aug 2022 19:53:22 +0530 Jeremy Stanley wrote ---

On 2022-08-08 19:45:23 +0530 (+0530), Ghanshyam Mann wrote: [...]

...

There were other cases also where template update have been missed or not corrct (for example independent release repo). That is why in Zed PTG, we agreed to remove these release specific template and auto generated patches to update the template name. From this cycle onwards, we will be doing these python version change in generic template at single place and do not need to update the python testing template name in every release.

Thanks for the reminder. Do you happen to know whether the release automation has been updated to accommodate this policy change?

Not yet, I have todo to do that and rebase my job template patch. Plan is that use the same auto-generated way to update the release specific template to generic one this time and from next release onwards we will update only generic template with proper notification to projects to make sure that new python versions jobs are working fine for their repo.

-gmann

-- Jeremy Stanley