[barbican][kolla][neutron][puppet-openstack][requirements] Please clean up Zuul configuration errors

Akihiro Motoki amotoki at gmail.com
Mon Jun 28 11:41:44 UTC 2021


Regarding neutron related errors, I see two patterns.

The one is "Unknown projects: openstack/networking-l2gw".
This is caused by the official retirement of networking-l2gw and
openstack/networking-l2gw was dropped from zuul/main.yaml.
We need to replace openstack/networking-l2gw with x/networking-l2gw.
This happens in networking-odl, networking-midonet and neutron-fwaas.

The other is "Job neutron-fwaas-networking-midonet-cross-py35 not defined".
This happens in neutron-fwaas.

I will take care of them.

Thanks,
Akihiro Motoki (amotoki)

On Sat, Jun 26, 2021 at 1:14 AM Jeremy Stanley <fungi at yuggoth.org> wrote:
>
> For the teams tagged in the subject, please have a look at
> https://zuul.opendev.org/t/openstack/config-errors and merge fixes
> to your respective repositories for the errors listed there. A
> summary view can also be found by clicking the "bell" icon in the
> top-right corner of https://zuul.opendev.org/t/openstack/status or
> similar pages).
>
> Many of these errors are new as of yesterday, due to lingering
> ansible_python_interpreter variable assignments left over from the
> Python 3.x default transition. Zuul no longer allows to override the
> value of this variable, but it can be safely removed since all cases
> seem to be setting it to the same as our current default.
>
> Roughly half the errors look like they've been there for longer, and
> seem to relate to project renames or job removals leaving stale
> references in other projects. In most cases you should simply be
> able to update the project names in these or remove the associated
> jobs as they're likely no longer used. Also be aware that many of
> these errors are on stable branches, so the cleanup will need
> backporting in such cases.
>
> Thanks for your prompt attention!
> --
> Jeremy Stanley



More information about the openstack-discuss mailing list