Skip to content

Synchronise 2025.1 with upstream#893

Merged
Alex-Welsh merged 1 commit into
stackhpc/2025.1from
upstream/2025.1-2026-06-29
Jun 29, 2026
Merged

Synchronise 2025.1 with upstream#893
Alex-Welsh merged 1 commit into
stackhpc/2025.1from
upstream/2025.1-2026-06-29

Conversation

@github-actions

Copy link
Copy Markdown

This PR contains a snapshot of 2025.1 from upstream stable/2025.1.

The playbook for migrating from `Redis` to `Valkey` fails as it targets
`all` hosts within the inventory. This means that during reconfiguration
of `Valkey` checks will fail as it attempts to perform `ping pong`
against hosts outside of the `valkey` group. This has been fixed by
limiting the playbook only to `valkey,redis` groups.

Closes-Bug: 2158356

Change-Id: I7baeab33ca8ba4372971d51500042628e3e14efa
Signed-off-by: Jack Hodgkiss <jack@stackhpc.com>
@github-actions github-actions Bot requested a review from a team as a code owner June 29, 2026 08:06
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels Jun 29, 2026
@Alex-Welsh Alex-Welsh merged commit f222b07 into stackhpc/2025.1 Jun 29, 2026
4 checks passed
@Alex-Welsh Alex-Welsh deleted the upstream/2025.1-2026-06-29 branch June 29, 2026 10:55
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.

2 participants