Skip to content

METAL-1726: Add yet another stage for ironic-image#8913

Merged
locriandev merged 1 commit intoopenshift-eng:openshift-4.22from
elfosardo:add-wheel-builder-ironic
Mar 17, 2026
Merged

METAL-1726: Add yet another stage for ironic-image#8913
locriandev merged 1 commit intoopenshift-eng:openshift-4.22from
elfosardo:add-wheel-builder-ironic

Conversation

@elfosardo
Copy link
Copy Markdown

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 10, 2026

@elfosardo: This pull request references METAL-1726 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@elfosardo
Copy link
Copy Markdown
Author

without this I think openshift/ironic-image#786 will break the internal builds

@elfosardo
Copy link
Copy Markdown
Author

cc @joepvd @locriandev
chicken'n'egg problem? :)

Copy link
Copy Markdown
Contributor

@locriandev locriandev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold

This change can only happen once ironic's Dockerfile grows an extra build layer, otherwise we'd have rebase failures and stop building it.

Apart from this, the correct syntax would be:

from:
  builder:
  - member: openshift-enterprise-base-rhel9-minimal
  - member: openshift-enterprise-base-rhel9-minimal
  member: openshift-enterprise-base-rhel9-minimal

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 11, 2026
@locriandev
Copy link
Copy Markdown
Contributor

@elfosardo the chicken'n'egg problem can be solved by merging this PR right after the ironic one :) Next build would find consistent config with upstream. Worst case scenario, we might miss some cycles.

@elfosardo
Copy link
Copy Markdown
Author

@locriandev ok so the "builder" entry it does not depend on the name of the stage, it's just a list?
I think I'm going to wait to have the minimal image in CI before moving forward in any case

@locriandev
Copy link
Copy Markdown
Contributor

@elfosardo that's right, builder is the allowed key and does not depend on the real stage name. also see the validator complaint

Comment thread images/ironic.yml Outdated
@elfosardo elfosardo force-pushed the add-wheel-builder-ironic branch from e0fe39e to 8ad18bc Compare March 13, 2026 13:30
@elfosardo elfosardo changed the title METAL-1726: Add yet another stage for ironic-image, the wheel-builder! METAL-1726: Add yet another stage for ironic-image Mar 13, 2026
@elfosardo elfosardo force-pushed the add-wheel-builder-ironic branch from 8ad18bc to d5b13b3 Compare March 13, 2026 13:33
@elfosardo elfosardo force-pushed the add-wheel-builder-ironic branch from d5b13b3 to e14ff15 Compare March 13, 2026 13:34
Copy link
Copy Markdown
Contributor

@locriandev locriandev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: locriandev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 13, 2026
@elfosardo
Copy link
Copy Markdown
Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2026

@elfosardo: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/art-pre-commit-check e14ff15 link false /test art-pre-commit-check

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@locriandev locriandev removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 17, 2026
@locriandev locriandev merged commit dc36eb1 into openshift-eng:openshift-4.22 Mar 17, 2026
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants