On 2021-11-12 19:32:17 +0100 (+0100), Radosław Piliszek wrote:

Please note ansible-collections-openstack is part of Ansible SIG, not OpenStack Ansible.

[...]

Interesting, I thought the Release Management team explicitly avoided handling releases for SIG repos, focusing solely on project team deliverables.

Hi, thanks for heads up. The first job failed because of the Zuul bug [1] and I didn't expect the job to run the second time, so I just released it manually to Galaxy. When the job tried the second time, it failed because it tried to duplicate the manual release. So I think it's all good now.

[1] https://review.opendev.org/c/zuul/zuul/+/817298

On Sat, Nov 13, 2021 at 9:05 AM Dmitriy Rabotyagov noonedeadpunk@ya.ru wrote:

• sshnaidm@

• все

Hi!

It's indeed OpenStack-Ansible SIG repo. But from what I can see - release is published in Ansible Galaxy which is the main thing that this job does. So for me things look good, but I guess the only person who for sure can verify that is Sagi Shnaidman.

Being able to tag repos is crucial for this sig since it's the only way to provide Ansible Collections in Ansible Galaxy.

12.11.2021, 17:33, "Előd Illés" elod.illes@est.tech:

Hi Openstack-Ansible team!

This mail is just to inform you that there was a release job failure [1] yesterday and the job could not be re-run as part of the job was finished successfully in the 1st run (so the 2nd attempt failed [2]).

Could you please review if everything is OK with the release?

Thanks,

Előd (elodilles @ #openstack-release)

[1]

http://lists.openstack.org/pipermail/release-job-failures/2021-November/0015... [2]

http://lists.openstack.org/pipermail/release-job-failures/2021-November/0015...

-- Kind Regards, Dmitriy Rabotyagov