Skip to content

Conversation

@qJkee
Copy link
Contributor

@qJkee qJkee commented Jan 7, 2026

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 Jan 7, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 7, 2026

@qJkee: This pull request references OCPEDGE-2292 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.

@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 7, 2026
@jeff-roche
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qJkee

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 Jan 7, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 7, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 7, 2026
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a57276f and 2 for PR HEAD d47e0e2 in total

@qJkee qJkee force-pushed the OCPEDGE-2292 branch 3 times, most recently from 67cf113 to 560ff50 Compare January 9, 2026 07:34
@codecov-commenter
Copy link

codecov-commenter commented Jan 9, 2026

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.20%. Comparing base (c070ca9) to head (f3bfb92).
⚠️ Report is 105 commits behind head on main.

Files with missing lines Patch % Lines
internal/csi/provisioner.go 0.00% 1 Missing ⚠️
internal/csi/snapshotter.go 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1898      +/-   ##
==========================================
+ Coverage   48.69%   49.20%   +0.50%     
==========================================
  Files          52       52              
  Lines        3709     3760      +51     
==========================================
+ Hits         1806     1850      +44     
- Misses       1753     1758       +5     
- Partials      150      152       +2     
Files with missing lines Coverage Δ
internal/csi/registrar.go 0.00% <ø> (ø)
internal/csi/provisioner.go 0.00% <0.00%> (ø)
internal/csi/snapshotter.go 0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@qJkee
Copy link
Contributor Author

qJkee commented Jan 9, 2026

/retest

@suleymanakbas91
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2026
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b6dc4cb and 2 for PR HEAD f3bfb92 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 13, 2026

@qJkee: 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 450178c into openshift:main Jan 13, 2026
17 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants