Skip to content

Synchronise 2023.1 with upstream#143

Open
github-actions[bot] wants to merge 1 commit into
stackhpc/2023.1from
upstream/2023.1-2026-05-25
Open

Synchronise 2023.1 with upstream#143
github-actions[bot] wants to merge 1 commit into
stackhpc/2023.1from
upstream/2023.1-2026-05-25

Conversation

@github-actions
Copy link
Copy Markdown

This PR contains a snapshot of 2023.1 from upstream unmaintained/2023.1.

A test in datera was failing locally due to the fact the the version
checking could be wrong in the egg-info local folder if you switch from
a branch to another.

It's not necessary to test this anymore as Cinder version 15 (train) is
EOL anyway.

Signed-off-by: Arnaud Morin <arnaud.morin@ovhcloud.com>
Change-Id: I0d17899c0b239ec969ff51238dcbd4402a567f6c
(cherry picked from commit 7ee7ac5)
(cherry picked from commit e70f1a8)
(cherry picked from commit b2298e1)
@github-actions github-actions Bot requested a review from a team as a code owner May 25, 2026 07:54
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant