Skip to content

OCPBUGS-74233: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine #1214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ncaak wants to merge 2 commits into
base: release-4.21
Choose a base branch
from
Open

OCPBUGS-74233: [bugfix] The ConfigMap value for StoragePath is ignored on basic routine #1214

ncaak wants to merge 2 commits into from
+70 −36

Conversation

@ncaak
Copy link
Contributor

@ncaak ncaak commented Jan 21, 2026

Manual cherry-pick of #1203

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 21, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 21, 2026

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

  • expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.21.z" 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:

Manual cherry-pick of #1203

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 added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 21, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 21, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ncaak
Copy link
Contributor Author

ncaak commented Jan 21, 2026

/test lint

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2026
@ncaak
Copy link
Contributor Author

ncaak commented Jan 21, 2026

/test ci/prow/lint

@openshift-ci
Copy link

openshift-ci bot commented Jan 21, 2026

@ncaak: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e

/test e2e-agnostic-upgrade

/test e2e-gcp-ovn-techpreview

/test images

/test insights-operator-conditions-gcp-ovn-techpreview

/test insights-operator-conditions-tests

/test insights-operator-e2e-tests

/test lint

/test okd-scos-images

/test unit

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-metal-ipi-ovn-ipv6

/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-insights-operator-master-e2e

pull-ci-openshift-insights-operator-master-e2e-agnostic-upgrade

pull-ci-openshift-insights-operator-master-e2e-gcp-ovn-techpreview

pull-ci-openshift-insights-operator-master-images

pull-ci-openshift-insights-operator-master-insights-operator-conditions-gcp-ovn-techpreview

pull-ci-openshift-insights-operator-master-insights-operator-conditions-tests

pull-ci-openshift-insights-operator-master-insights-operator-e2e-tests

pull-ci-openshift-insights-operator-master-lint

pull-ci-openshift-insights-operator-master-okd-scos-images

pull-ci-openshift-insights-operator-master-unit

pull-ci-openshift-insights-operator-master-verify-deps
Details

In response to this:

/test ci/prow/lint

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.

@ncaak ncaak changed the base branch from master to release-4.21 January 21, 2026 16:04
@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 21, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 21, 2026

@ncaak: This pull request references Jira Issue OCPBUGS-74233, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-66386 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-66386 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @BaiyangZhou

Details

In response to this:

Manual cherry-pick of #1203

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 a review from BaiyangZhou January 21, 2026 16:04
@ncaak ncaak marked this pull request as ready for review January 21, 2026 16:11
@openshift-ci
Copy link

openshift-ci bot commented Jan 21, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncaak

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 removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 21, 2026
@ncaak
Copy link
Contributor Author

ncaak commented Jan 21, 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 Jan 21, 2026
@ncaak
Copy link
Contributor Author

ncaak commented Jan 21, 2026

/verified later @BaiyangZhou

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Jan 21, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 21, 2026

@ncaak: This PR has been marked to be verified later by @BaiyangZhou.

Details

In response to this:

/verified later @BaiyangZhou

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

BaiyangZhou commented Jan 22, 2026

/test e2e-gcp-ovn-techpreview

1 similar comment
@BaiyangZhou
Copy link

BaiyangZhou commented Jan 22, 2026

/test e2e-gcp-ovn-techpreview

@opokornyy
Copy link
Contributor

opokornyy commented Jan 22, 2026

/retest

@ncaak
Copy link
Contributor Author

ncaak commented Jan 22, 2026

/test lint

@openshift-ci
Copy link

openshift-ci bot commented Jan 22, 2026

@ncaak: 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/lint 4cac87f link true /test lint

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

Reviewers

@BaiyangZhou BaiyangZhou Awaiting requested review from BaiyangZhou

@katushiik11 katushiik11 Awaiting requested review from katushiik11

@opokornyy opokornyy Awaiting requested review from opokornyy

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@ncaak @openshift-ci-robot @BaiyangZhou @opokornyy