Skip to content

Conversation

@yingwang-0320
Copy link
Contributor

No description provided.

@openshift-ci
Copy link

openshift-ci bot commented Dec 2, 2025

@yingwang-0320: all tests passed!

Full PR test history. Your PR dashboard.

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.

@yingwang-0320
Copy link
Contributor Author

@yingwang-0320 yingwang-0320 changed the title fix LEVEL0 case failure OCP-28633 OCPQE-31199: fix LEVEL0 case failure OCP-28633 Dec 2, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 2, 2025

@yingwang-0320: This pull request references OCPQE-31199 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 bug to target the "4.21.0" version, but no target version was set.

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.

@asood-rh
Copy link
Contributor

asood-rh commented Dec 2, 2025

Change looks good as the test is passing.
@yingwang-0320 What caused the change to be introduced?

@yingwang-0320
Copy link
Contributor Author

yingwang-0320 commented Dec 3, 2025

Hi @asood-rh , it's level0 case, and it fails when testing 4.18 as decribed in https://issues.redhat.com/browse/OCPQE-31199

@asood-rh
Copy link
Contributor

asood-rh commented Dec 4, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 4, 2025
@asood-rh
Copy link
Contributor

asood-rh commented Dec 4, 2025

Change looks good as the test is passing. @yingwang-0320 What caused the change to be introduced?

Thanks, should have traced it to OCPQE id that you had in title.

@zhaozhanqi
Copy link
Contributor

/approve

@zhaozhanqi
Copy link
Contributor

/assign @pruan-rht @liangxia

@pruan-rht
Copy link
Member

/lgtm
/approve

@openshift-ci
Copy link

openshift-ci bot commented Dec 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asood-rh, pruan-rht, zhaozhanqi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Dec 4, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 0ff4171 into openshift:main Dec 4, 2025
2 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants