Update Neutron image

[dougszumski]

Pulls in various changes from upstream sync

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: stackhpc/stackhpc-kayobe-config/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 93af43b2-e0c6-41c6-884e-51b63d8dc2ff

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: stackhpc/stackhpc-kayobe-config/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 705cb53b-06b6-4f2b-a09f-7e324ed3a757

📥 Commits

Reviewing files that changed from the base of the PR and between 4d60ec6 and b816fff.

📒 Files selected for processing: 1

• etc/kayobe/kolla-image-tags.yml

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

📝 Walkthrough

Neutron image tags for Rocky Linux 10 and Ubuntu Noble changed from build 20261009T164731 to 20261012T162149.

Changes: Neutron image tags

Layer / File(s)	Summary
Update Neutron image tags etc/kayobe/kolla-image-tags.yml	The Rocky Linux 10 and Ubuntu Noble Neutron image tags now use build 20261012T162149.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to b816f

This PR advances the Rocky Linux 10 and Ubuntu Noble Neutron image tags. No concrete merge-blocking issue is evident; the normal checks should confirm the tags are available.

Pre-merge checks: 3

Passed checks: 3 passed

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.

• 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.}

[Alex-Welsh]

I think at some point we had a rule that any new container needs a reno. I also think it's an important time to be adding them right now, since we're going to move to the new release format soon where they'll be more valuabale

[jovial]

Sorry, the copilot button went rogue and changed this without asking

[Alex-Welsh]

I think at some point we had a rule that any new container needs a reno. I also think it's an important time to be adding them right now, since we're going to move to the new release format soon where they'll be more valuabale

A CI check would be handy to enforce that - sorry, didn't realise we'd made it a rule.

I've been looking at doing just that, having a CI check to prompt people about release notes. It's one of those "rules" that was talked about years ago but never written down, so doesn't get enforced all the time. I'll write out some proper guidelines as well

[bbezak]

@dougszumski Hi, I can see that tests here were cancelled here? stackhpc/neutron#364. are we sure that neutron tests were fine?

[dougszumski]

@dougszumski Hi, I can see that tests here were cancelled here? stackhpc/neutron#364. are we sure that neutron tests were fine?

Thanks @bbezak - I'm not sure why they were cancelled. I've triggered another run here - couldn't get it going again on this PR for some reason

https://zuul.stackhpc.com/t/stackhpc/status/change/366,fe40f6922f41a7e2c7638be0878c8bb1dad27a98

[dougszumski]

@dougszumski Hi, I can see that tests here were cancelled here? stackhpc/neutron#364. are we sure that neutron tests were fine?

Thanks @bbezak - I'm not sure why they were cancelled. I've triggered another run here - couldn't get it going again on this PR for some reason

https://zuul.stackhpc.com/t/stackhpc/status/change/366,fe40f6922f41a7e2c7638be0878c8bb1dad27a98

Zuul tests passed:

https://github.com/stackhpc/neutron/pull/366/checks?check_run_id=116347271689