Bump Keystone images to fix CVE-2026-33551 (Yoga) #6763
seunghun1eestackhpc-pull-request.yml
on: pull_request
Check changed files
4s
Matrix: tox
aio (CentOS OVN)
/
All in one
aio (CentOS OVS)
/
All in one
aio (Rocky 9 OVN)
/
All in one
aio (Rocky 9 OVS)
/
All in one
aio (Rocky OVN)
/
All in one
aio (Rocky OVS)
/
All in one
aio (Ubuntu Jammy OVN)
/
All in one
aio (Ubuntu Jammy OVS)
/
All in one
aio (Ubuntu OVN)
/
All in one
aio (Ubuntu OVS)
/
All in one
Annotations
6 errors and 5 warnings
|
Tox docs with Python 3.8
Process completed with exit code 2.
|
|
Tox pep8 with Python 3.8
The strategy configuration was canceled because "tox.docs_3_8" failed
|
|
Tox pep8 with Python 3.8
Process completed with exit code 2.
|
|
Tox releasenotes with Python 3.8
The strategy configuration was canceled because "tox.docs_3_8" failed
|
|
Tox releasenotes with Python 3.8
Process completed with exit code 2.
|
|
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 docs with Python 3.8
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.8
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 releasenotes with Python 3.8
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/
|