Wallaby install fails after renaming the openstack branches to "unmaintained"

Bug #2066932 reported by Laszlo Budai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
New
Undecided
Unassigned

Bug Description

We have a pipeline that installs OpenStack Wallaby using OpenStack Ansible. Our pipeline stopped working since the OpenStack Repository has renamed the "stable/wallaby" branch to "unmaintained/wallaby".

The failure happens in the task: [python_venv_build : Build wheels for the packages to be installed into the venv], and the error is:

fatal: [controller1_keystone_container-41c6b135 -> 192.168.100.197]: FAILED! => {"attempts": 5, "changed": true, "cmd": ["/openstack/venvs/wheel-builder-python3/bin/pip", "wheel", "--requirement", "/var/www/repo/os-releases/23.4.5.dev3/ubuntu-20.04-x86_64/requirements/keystone-23.4.5.dev3-requirements.txt", "--constraint", "/var/www/repo/os-releases/23.4.5.dev3/ubuntu-20.04-x86_64/requirements/keystone-23.4.5.dev3-global-constraints.txt", "--constraint", "/var/www/repo/os-releases/23.4.5.dev3/ubuntu-20.04-x86_64/requirements/keystone-23.4.5.dev3-source-constraints.txt", "--wheel-dir", "/tmp/keystone-23.4.5.dev3/", "--find-links", "/var/www/repo/os-releases/23.4.5.dev3/ubuntu-20.04-x86_64/wheels/", "--log", "/var/log/python_wheel_build.log"], "delta": "0:00:05.974445", "end": "2024-05-22 14:48:19.081279", "msg": "non-zero return code", "rc": 1, "start": "2024-05-22 14:48:13.106834", "stderr": " Running command git clone -q https://github.com/openstack/keystone /tmp/pip-wheel-m_okif5u/keystone_3fc6eb12bb9a4130ac1f5d19b9b01ed6\n WARNING: Did not find branch or tag 'stable/wallaby', assuming revision or ref.\n Running command git checkout -q stable/wallaby\n error: pathspec 'stable/wallaby' did not match any file(s) known to git\nWARNING: Discarding git+https://github.com/openstack/keystone@stable/wallaby#egg=keystone. Command errored out with exit status 1: git checkout -q stable/wallaby Check the logs for full command output.\nERROR: Could not find a version that satisfies the requirement keystone (unavailable)\nERROR: No matching distribution found for keystone (unavailable)\nWARNING: You are using pip version 21.0.1; however, version 24.0 is available.\nYou should consider upgrading via the '/openstack/venvs/wheel-builder-python3/bin/python -m pip install --upgrade pip' command.", "stderr_lines": [" Running command git clone -q https://github.com/openstack/keystone /tmp/pip-wheel-m_okif5u/keystone_3fc6eb12bb9a4130ac1f5d19b9b01ed6", " WARNING: Did not find branch or tag 'stable/wallaby', assuming revision or ref.", " Running command git checkout -q stable/wallaby", " error: pathspec 'stable/wallaby' did not match any file(s) known to git", "WARNING: Discarding git+https://github.com/openstack/keystone@stable/wallaby#egg=keystone. Command errored out with exit status 1: git checkout -q stable/wallaby Check the logs for full command output.", "ERROR: Could not find a version that satisfies the requirement keystone (unavailable)", "ERROR: No matching distribution found for keystone (unavailable)", "WARNING: You are using pip version 21.0.1; however, version 24.0 is available.", "You should consider upgrading via the '/openstack/venvs/wheel-builder-python3/bin/python -m pip install --upgrade pip' command."], "stdout": "Looking in links: /var/www/repo/os-releases/23.4.5.dev3/ubuntu-20.04-x86_64/wheels/\nCollecting keystone\n Cloning https://github.com/openstack/keystone (to revision stable/wallaby) to /tmp/pip-wheel-m_okif5u/keystone_3fc6eb12bb9a4130ac1f5d19b9b01ed6", "stdout_lines": ["Looking in links: /var/www/repo/os-releases/23.4.5.dev3/ubuntu-20.04-x86_64/wheels/", "Collecting keystone", " Cloning https://github.com/openstack/keystone (to revision stable/wallaby) to /tmp/pip-wheel-m_okif5u/keystone_3fc6eb12bb9a4130ac1f5d19b9b01ed6"]}

For us it helped to change all the "stable/wallaby" occurrences to "unmaintained/wallaby" in the `ansible-role-requirements.yml` and `playbooks/defaults/repo_packages/openstack_services.yml` files.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.