Skip to content

Bump Keystone images to fix CVE-2026-33551 (Antelope) #6786

Bump Keystone images to fix CVE-2026-33551 (Antelope)

Bump Keystone images to fix CVE-2026-33551 (Antelope) #6786

Triggered via pull request April 7, 2026 15:00
Status Failure
Total duration 3m 45s
Artifacts

stackhpc-pull-request.yml

on: pull_request
Check changed files
18s
Check changed files
Matrix: tox
Build Kayobe Image  /  Build kayobe image
3m 14s
Build Kayobe Image / Build kayobe image
Check container image tags  /  Check container image tags
Check container image tags / Check container image tags
aio (Rocky 9 OVN)  /  All in one
aio (Rocky 9 OVN) / All in one
aio (Rocky 9 OVS)  /  All in one
aio (Rocky 9 OVS) / All in one
aio (Ubuntu Jammy OVN)  /  All in one
aio (Ubuntu Jammy OVN) / All in one
aio (Ubuntu Jammy OVS)  /  All in one
aio (Ubuntu Jammy OVS) / All in one
aio upgrade (Rocky 9 OVN)  /  All in one
aio upgrade (Rocky 9 OVN) / All in one
aio upgrade (Ubuntu Jammy OVS)  /  All in one
aio upgrade (Ubuntu Jammy OVS) / All in one
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
Build Kayobe Image / Build kayobe image
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c sudo cp -rfp /src /tmp/ && sudo chown -Rf stack:stack /tmp/src && grep -lR \"\\$ANSIBLE_VAULT\" /tmp/src | xargs rm -f && bash /tmp/src/.automation/utils/kayobe-automation-install && (rm -f /stack/.ssh/{id_rsa,id_rsa.pub} || true) && (mkdir /stack/.ansible || true) && (cp -rfp /stack/kayobe-automation-env/src/kayobe-config/etc/kayobe/ansible/roles /stack/.ansible/kayobe-automation-roles || true) && (cp -rfp /stack/kayobe-automation-env/src/kayobe-config/etc/kayobe/ansible/collections /stack/.ansible/kayobe-automation-collections || true) && rm -rf /stack/kayobe-automation-env/src/kayobe-config" did not complete successfully: exit code: 1
Check changed files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Tox releasenotes with Python 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Tox docs with Python 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Tox pep8 with Python 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build Kayobe Image / Build kayobe image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, docker/build-push-action@v5, docker/login-action@v3, docker/metadata-action@v5, docker/setup-buildx-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/