Comment 1 for bug 2055417

Hey,

Yes, eventually right now there's quite some hassle with unmaintained/yoga.
This is the brand new process introduced by OpenStack Technical Committee lately: https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html

So stable/yoga branch was replaced with unmaintained/yoga. As quite un-obvious pitfall for us was that current OpenStack-Ansible core team has no access to the unmaintained/yoga branch by design of the TC decision.
At the moment of re-naming we made an assumption to fix SHAs and things in our bootstrap process to refer unmaintained/yoga after branch being renamed, but we are unable to do so.

Frankly speaking, I'm not sure if openstack-ansible-plugins is the only thing that points to stable/yoga or there're more things/services doing so.
Of course, you can try to create /etc/openstack_deploy/user-collection-requirements.yml file with content:

collections:
- name: https://opendev.org/openstack/openstack-ansible-plugins
  version: yoga-eom
  type: git

This supposedly will fix the bootstrap process.

But eventually, we would suggest upgrading to any supported brach. Just in case, upgrade to stable/2023.1 is supported directly from stable/yoga as well. So you can jump through Zed.

Sorting out privileges to unmaintained/yoga may take a while though, especially now when 2024.1 release is that close.