Skip to content

microshift-bootc hermetic - 4.22#8993

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-eng:openshift-4.22from
fgallott:microshift-bootc-hermetic
Feb 19, 2026
Merged

microshift-bootc hermetic - 4.22#8993
openshift-merge-bot[bot] merged 1 commit intoopenshift-eng:openshift-4.22from
fgallott:microshift-bootc-hermetic

Conversation

@fgallott
Copy link

fixed in main upstream openshift/microshift#5824

test build

@fgallott
Copy link
Author

/label ackowledge-critical-fixes-only

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

@fgallott: The label(s) /label ackowledge-critical-fixes-only cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label ackowledge-critical-fixes-only

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.

@fgallott
Copy link
Author

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Feb 18, 2026
@fgallott
Copy link
Author

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

@openshift-cherrypick-robot

@fgallott: once the present PR merges, I will cherry-pick it on top of openshift-4.18, openshift-4.19, openshift-4.20, openshift-4.21, openshift-4.23, openshift-5.0 in new PRs and assign them to you.

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

@lgarciaaco
Copy link
Contributor

/lgtm
/cherry-pick openshift-4.23
/cherry-pick openshift-4.21

@openshift-cherrypick-robot

@lgarciaaco: once the present PR merges, I will cherry-pick it on top of openshift-4.21, openshift-4.23 in new PRs and assign them to you.

Details

In response to this:

/lgtm
/cherry-pick openshift-4.23
/cherry-pick openshift-4.21

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 19, 2026
@fgallott
Copy link
Author

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgallott

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 Feb 19, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit a3b4706 into openshift-eng:openshift-4.22 Feb 19, 2026
2 checks passed
@openshift-cherrypick-robot

@fgallott: new pull request created: #9024

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

@openshift-cherrypick-robot

@fgallott: new pull request created: #9025

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

@openshift-cherrypick-robot

@fgallott: new pull request created: #9026

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

@openshift-cherrypick-robot

@fgallott: new pull request created: #9027

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

@openshift-cherrypick-robot

@fgallott: new pull request created: #9028

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

@openshift-cherrypick-robot

@fgallott: new pull request created: #9030

Details

In response to this:

/cherrypick openshift-5.0
/cherrypick openshift-4.23
/cherrypick openshift-4.21
/cherrypick openshift-4.20
/cherrypick openshift-4.19
/cherrypick openshift-4.18

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.

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

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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