./scripts/bootstrap-ansible.sh for yoga does not work anymore ...

[Peter Struys]

Hi,

We are probably missing something due to our ignorance ...

We were on OpenStack-Ansible yoga - tag 25.2 - and we tried a 'git checkout stable/yoga', 'git checkout 25.6.0' and 'git checkout unmaintained/yoga' (which all are allowed) to upgrade to the latest yoga but for none of these the script './scripts/bootstrap-ansible.sh' will work. We always get an error "error: pathspec 'stable/yoga' did not match any file(s) known to git". And indeed on https://opendev.org/openstack/openstack-ansible-plugins there is no longer a stable/yoga but there is unmaintainded/yoga ?

Does this have to do with yoga being "unmaintained" at the moment ? Is this temporarily ? What does 'unmaintained" mean ? We do see a stable/xena which is older.

Is our only option to go forward to "stable/zed" ?

thank you
Peter

[Dmitriy Rabotyagov (noonedeadpunk)]

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.

[Peter Struys (peterstruys)]

Hi,

Thank you for confirming that the tag unmaintained/yoga is causing these problems. I was able to use the workaround with /etc/openstack_deploy/user-collection-requirements.yml and branch yoga-eom to run the playbooks as described in "minor upgrades".

We will probably moving soon to zed or even higher as described in "major upgrades".

thank you for the prompt and extensive reply.

regards
Peter

[Dmitriy Rabotyagov (noonedeadpunk)]

This patch should be covering the issue partially: https://review.opendev.org/c/openstack/openstack-ansible/+/911621

OpenStack-Ansible team still don't have privileges to land this fix though.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible/+/911621
Committed: https://opendev.org/openstack/openstack-ansible/commit/06de2bbcfc7f13c4bbb1ef6f0eae723614da5293
Submitter: "Zuul (22348)"
Branch: unmaintained/yoga

commit 06de2bbcfc7f13c4bbb1ef6f0eae723614da5293
Author: Jonathan Rosser <email address hidden>
Date: Wed Mar 6 16:59:21 2024 +0000

    Update branch names to reflect move from stable to unmaintained branch names

    Closes-Bug: #2055417
    Change-Id: Id662cae18ad010fe447b1187471aac2a279ce6ea