Skip to content

Synchronise 2025.1 with upstream - #948

Merged
Alex-Welsh merged 1 commit into
stackhpc/2025.1from
upstream/2025.1-2026-09-21
Sep 21, 2026
Merged

Alex-Welsh merged 1 commit into
stackhpc/2025.1from
upstream/2025.1-2026-09-21

Conversation

@github-actions

Copy link
Copy Markdown

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

Ansible's "is string" Jinja test returns False for values encrypted
with ansible-vault (AnsibleVaultEncryptedUnicode), so a precheck
using such an encrypted password/salt failed incorrectly. Accept the
value if it is either a plain string or vault_encrypted.

Closes-Bug: #2115495
Change-Id: I0bf783c40ca5be66717193be9dece971805fca55
Signed-off-by: fprzewozn <przewozny.franciszek@gmail.com>
(cherry picked from commit ed74de7)
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels Sep 21, 2026
@github-actions
github-actions Bot requested a review from a team as a code owner September 21, 2026 06:49
@Alex-Welsh
Alex-Welsh merged commit abe90e0 into stackhpc/2025.1 Sep 21, 2026
4 checks passed
@Alex-Welsh
Alex-Welsh deleted the upstream/2025.1-2026-09-21 branch September 21, 2026 13:35
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