Skip to content

Use StackHPC Ironic fork - #2739

Draft
TBExtent wants to merge 1 commit into
stackhpc/2026.1from
gazpacho-ironic-fork
Draft

TBExtent wants to merge 1 commit into
stackhpc/2026.1from
gazpacho-ironic-fork

Conversation

@TBExtent

@TBExtent TBExtent commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Switch to the Ironic fork, so that automated upstream syncs can be configured ahead of providing networking patches for redfish-virtual-media

Switch to the Ironic fork, so that automated upstream syncs can be configured ahead of providing networking patches for redfish-virtual-media
@TBExtent
TBExtent requested a review from a team as a code owner November 2, 2026 15:48
@github-actions github-actions Bot added the waiting-review PR is waiting for a review label Nov 2, 2026
@coderabbitai

coderabbitai Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between 6d2d65b and fd0e906.

Files selected for processing: 1
  • etc/kayobe/kolla.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

The Kolla source mapping adds ironic-base from the StackHPC Ironic repository, using a reference based on openstack_release.

Changes: Ironic source configuration

Layer / File(s) Summary
Add ironic-base source
etc/kayobe/kolla.yml
The kolla_sources mapping defines ironic-base with the StackHPC Ironic repository and the stackhpc/{{ openstack_release }} reference.

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

Merge Risk: Minimal · up to fd0e9

The Ironic source now uses the StackHPC fork, and the default release branch exists. No actionable merge-blocking risk remains after normal checks.

Pre-merge checks: Passed 3
Check name Status Explanation
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 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

@Alex-Welsh

Copy link
Copy Markdown
Member

@TBExtent please also rebuild images and add a reno

@TBExtent
TBExtent marked this pull request as draft November 3, 2026 10:22
@github-actions github-actions Bot added waiting-author-response PR is waiting for the author to respond and removed waiting-review PR is waiting for a review labels Nov 3, 2026
@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Happy Friday @TBExtent, this is a friendly reminder that this PR is waiting for your changes or response. Please take a look when you have a moment!

Note: Once your changes are ready, remove the waiting-author-response label and add the waiting-review label.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-author-response PR is waiting for the author to respond

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants