Skip to content

[release-4.18] OCPBUGS-76537: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine#1228

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-1224-to-release-4.18
Open

[release-4.18] OCPBUGS-76537: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine#1228
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-1224-to-release-4.18

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #1224

/assign ncaak

@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-75902 has been cloned as Jira Issue OCPBUGS-76537. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-76537: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine

Details

In response to this:

This is an automated cherry-pick of #1224

/assign ncaak

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 changed the title [release-4.18] OCPBUGS-75902: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine [release-4.18] OCPBUGS-76537: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine Feb 11, 2026
@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 11, 2026
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-76537, which is invalid:

  • expected dependent Jira Issue OCPBUGS-75902 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1224

/assign ncaak

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 openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 11, 2026
@openshift-ci openshift-ci bot requested review from ncaak and tremes February 11, 2026 09:38
@openshift-ci
Copy link

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please ask for approval from ncaak. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@ncaak
Copy link
Contributor

ncaak commented Feb 11, 2026

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 11, 2026
@ncaak
Copy link
Contributor

ncaak commented Feb 11, 2026

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@ncaak: This pull request references Jira Issue OCPBUGS-76537, which is invalid:

  • expected dependent Jira Issue OCPBUGS-75902 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

@BaiyangZhou
Copy link

/retest

@openshift-ci
Copy link

openshift-ci bot commented Feb 12, 2026

@openshift-cherrypick-robot: The following tests 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/images 75db7b5 link true /test images
ci/prow/lint 75db7b5 link true /test lint
ci/prow/e2e-agnostic-upgrade 75db7b5 link true /test e2e-agnostic-upgrade
ci/prow/insights-operator-e2e-tests 75db7b5 link true /test insights-operator-e2e-tests
ci/prow/e2e 75db7b5 link true /test e2e
ci/prow/unit 75db7b5 link true /test unit
ci/prow/okd-scos-images 75db7b5 link true /test okd-scos-images
ci/prow/e2e-gcp-ovn-techpreview 75db7b5 link true /test e2e-gcp-ovn-techpreview

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.

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

Labels

backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments