fix(ceph-provisioners): create deployment namespace

[Tadas Sutkaitis (fitbeard)]

What changed

• create the configured Ceph provisioners namespace before creating Kubernetes resources;
• add a release note.

Why

The role assumed its namespace had been created by an earlier deployment step. That hidden ordering dependency breaks focused deployments and makes the role non-self-contained.

This production fix is extracted from #4152 so it can be reviewed, released, and backported independently from selective CI.

Validation

• file-scoped pre-commit hooks passed;
• git diff --check passed;
• the repository-wide Ansible lint traversal reached all roles and only failed on the existing galaxy[no-changelog] metadata issue;
• Reno parsed the new note and only reported the repository's existing duplicate release-note UID.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 806b13c8da

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "Codex (@codex) review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".

[chatgpt-codex-connector]

Create the namespace used by the prerequisite resources

When ceph_provisioners_helm_release_namespace is overridden and openstack does not already exist, this creates only the configured namespace, but the following Service, Endpoints, and Secret still specify namespace: openstack at lines 51, 75, and 112. In the focused-deployment scenario this change is intended to fix, the Service creation therefore still fails because its namespace is absent; use the configured namespace consistently for those resources.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Replace the escaped newline with a real line break

YAML block scalars preserve this literal \n, so the generated release notes display a backslash and n in the middle of the sentence rather than wrapping normally. Replace it with an actual source line break so the user-facing note is natural English.

AGENTS.md reference: AGENTS.md:L20-L20

Useful? React with 👍 / 👎.

[Tadas Sutkaitis (fitbeard)]

recheck

[Tadas Sutkaitis (fitbeard)]

recheck

[Tadas Sutkaitis (fitbeard)]

recheck

[vexxhost-bot]

Successfully created backport PR for stable/zed:

• [Backport stable/zed] fix(ceph-provisioners): create deployment namespace #4303

[vexxhost-bot]

Successfully created backport PR for stable/2023.1:

• [Backport stable/2023.1] fix(ceph-provisioners): create deployment namespace #4308

[vexxhost-bot]

Successfully created backport PR for stable/2023.2:

• [Backport stable/2023.2] fix(ceph-provisioners): create deployment namespace #4313

[vexxhost-bot]

Successfully created backport PR for stable/2024.1:

• [Backport stable/2024.1] fix(ceph-provisioners): create deployment namespace #4318

[vexxhost-bot]

Successfully created backport PR for stable/2024.2:

• [Backport stable/2024.2] fix(ceph-provisioners): create deployment namespace #4323

[vexxhost-bot]

Successfully created backport PR for stable/2025.1:

• [Backport stable/2025.1] fix(ceph-provisioners): create deployment namespace #4327

[vexxhost-bot]

Successfully created backport PR for stable/2025.2:

• [Backport stable/2025.2] fix(ceph-provisioners): create deployment namespace #4330