Skip to content

OTA-1928: cincinnati-graph-data: add a new test validate-release#77277

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
hongkailiu:test-validate
Apr 2, 2026
Merged

OTA-1928: cincinnati-graph-data: add a new test validate-release#77277
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
hongkailiu:test-validate

Conversation

@hongkailiu
Copy link
Copy Markdown
Member

@hongkailiu hongkailiu commented Apr 2, 2026

The code is https://github.com/hongkailiu/test-go/tree/validate-release
The image is pushed to quay.io/openshift-ota/cincinnati-ci-public:validate-release

The job is optional so that it wont block while I do iterations after merging.

I will move the src to the right place when this is done. https://redhat.atlassian.net/browse/OTA-1850

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 2, 2026

@hongkailiu: This pull request references OTA-1928 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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 2, 2026
@openshift-ci openshift-ci bot requested review from DavidHurta and fao89 April 2, 2026 00:28
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@hongkailiu: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-cincinnati-graph-data-master-validate-release openshift/cincinnati-graph-data presubmit Presubmit changed
pull-ci-openshift-cincinnati-graph-data-master-e2e openshift/cincinnati-graph-data presubmit Ci-operator config changed
pull-ci-openshift-cincinnati-graph-data-master-e2e-latest-cincinnati openshift/cincinnati-graph-data presubmit Ci-operator config changed
pull-ci-openshift-cincinnati-graph-data-master-images openshift/cincinnati-graph-data presubmit Ci-operator config changed
pull-ci-openshift-cincinnati-graph-data-master-stabilization-bot-tests openshift/cincinnati-graph-data presubmit Ci-operator config changed
pull-ci-openshift-cincinnati-graph-data-master-validate-blocked-edges openshift/cincinnati-graph-data presubmit Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Apr 2, 2026

@hongkailiu: This pull request references OTA-1928 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:

The code is https://github.com/hongkailiu/test-go/tree/validate-release
The image is pushed to quay.io/openshift-ota/cincinnati-ci-public:validate-release

The job is optional so that I can iterate after merging.

I will move the src to the right place when this is done. https://redhat.atlassian.net/browse/OTA-1850

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
Copy Markdown
Contributor

openshift-ci-robot commented Apr 2, 2026

@hongkailiu: This pull request references OTA-1928 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:

The code is https://github.com/hongkailiu/test-go/tree/validate-release
The image is pushed to quay.io/openshift-ota/cincinnati-ci-public:validate-release

The job is optional so that it wont block while I do iterations after merging.

I will move the src to the right place when this is done. https://redhat.atlassian.net/browse/OTA-1850

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
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 2, 2026

@hongkailiu: 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.

@hongkailiu
Copy link
Copy Markdown
Member Author

/pj-rehearse skip

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@hongkailiu: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 2, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, liangxia

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 Apr 2, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 9f963e1 into openshift:main Apr 2, 2026
16 checks passed
vimauro pushed a commit to vimauro/release that referenced this pull request Apr 2, 2026
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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants