feat: bump magnum-capi-helm to v1.4.0

[jackhodgkiss]

Update magnum-capi-helm to v1.4.0 which resolves an issue with a tenant cluster being incorrectly reported as unhealthy.

[coderabbitai]

📝 Walkthrough

The configuration adds Magnum image tags for Rocky 10 and Ubuntu Noble, updates the Magnum CAPI Helm driver pin to v1.4.0, and adds a release note about the upgrade and a tenant-cluster health fix.

Changes: Magnum configuration and release note

Layer / File(s)	Summary
Update Magnum image and driver versions etc/kayobe/kolla.yml, etc/kayobe/kolla-image-tags.yml, releasenotes/notes/*	The configuration pins magnum-capi-helm to v1.4.0 and adds Magnum image tags for Rocky 10 and Ubuntu Noble. The release note records the upgrade and a fix for tenant clusters reported as unhealthy.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: 🟡 Moderate · up to 4044f

Promote both Magnum tags before merging and deploying this update; otherwise production image sync or the Magnum rollout can fail because the tags are missing.

Pre-merge checks: 3

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[jackhodgkiss]

Awaiting new magnum image builds

https://github.com/stackhpc/stackhpc-kayobe-config/actions/runs/37649977015

[Alex-Welsh]

rebased re-rebuild build is building http://github.com/stackhpc/stackhpc-kayobe-config/actions/runs/38230957685

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Repository: stackhpc/stackhpc-kayobe-config/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: e7df6b39-8a2f-494c-9b7b-2ebf569c5274

📥 Commits

Reviewing files that changed from the base of the PR and between fe4e839 and 4044fa2.

📒 Files selected for processing: 3

• etc/kayobe/kolla-image-tags.yml
• etc/kayobe/kolla.yml
• releasenotes/notes/bump-magnum-capi-helm-1a6bd663a5c397ee.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

[coderabbitai]

🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Promote both Magnum tags before merging this mapping.

The observed promotion used the base mapping, which has no magnum entry. It therefore did not copy these tags from stackhpc-dev to stackhpc. The production tag check rejects missing tags, and Magnum deployment can fail if it runs before a later promotion. Merging only queues an asynchronous promotion and does not gate production sync or deployment. Promote both tags before merging this change.