Skip to content

Conversation

@dtantsur
Copy link
Member

If the ConfigMap is mounted as optional, it will end up in an empty
directory, and cat dir/* will fail on it.

Signed-off-by: Dmitry Tantsur dtantsur@protonmail.com
(cherry picked from commit a1495fc)

If the ConfigMap is mounted as optional, it will end up in an empty
directory, and `cat dir/*` will fail on it.

Signed-off-by: Dmitry Tantsur <dtantsur@protonmail.com>
(cherry picked from commit a1495fc)
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 23, 2025

@dtantsur: This pull request references METAL-1104 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 spike to target the "4.21.0" version, but no target version was set.

Details

In response to this:

If the ConfigMap is mounted as optional, it will end up in an empty
directory, and cat dir/* will fail on it.

Signed-off-by: Dmitry Tantsur dtantsur@protonmail.com
(cherry picked from commit a1495fc)

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.

@openshift-ci openshift-ci bot requested review from bfournie and elfosardo November 23, 2025 18:38
@openshift-ci
Copy link

openshift-ci bot commented Nov 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtantsur

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 Nov 23, 2025
@dtantsur
Copy link
Member Author

/retest

1 similar comment
@dtantsur
Copy link
Member Author

/retest

@elfosardo
Copy link

/test images

1 similar comment
@iurygregory
Copy link

/test images

@iurygregory
Copy link

/retest-required

@iurygregory
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 25, 2025
@elfosardo
Copy link

/retest

1 similar comment
@dtantsur
Copy link
Member Author

/retest

@dtantsur
Copy link
Member Author

/verified by @dtantsur

I've tested this patch on dev-scripts together with openshift/cluster-baremetal-operator#527 and the older merged installer patch, both with and without openshift-metal3/dev-scripts#1812.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 25, 2025
@openshift-ci-robot
Copy link

@dtantsur: This PR has been marked as verified by @dtantsur.

Details

In response to this:

/verified by @dtantsur

I've tested this patch on dev-scripts together with openshift/cluster-baremetal-operator#527 and the older merged installer patch, both with and without openshift-metal3/dev-scripts#1812.

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8884415 and 2 for PR HEAD 3be4fe1 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9c883d0 and 1 for PR HEAD 3be4fe1 in total

@dtantsur
Copy link
Member Author

/test e2e-metal-ipi-bm

1 similar comment
@dtantsur
Copy link
Member Author

/test e2e-metal-ipi-bm

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f19c445 and 0 for PR HEAD 3be4fe1 in total

@openshift-ci-robot
Copy link

/hold

Revision 3be4fe1 was retested 3 times: holding

@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 Nov 27, 2025
@dtantsur
Copy link
Member Author

/hold cancel
/retest

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 27, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 27, 2025

@dtantsur: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit c6ead01 into openshift:main Nov 27, 2025
8 checks passed
@dtantsur dtantsur deleted the bmc-ca-oc branch November 27, 2025 17:22
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants