Skip to content

OCPBUGS-56045: OLMv1: Update test bundles [release-4.19] #29836

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
wants to merge 1 commit into
base: release-4.19
Choose a base branch
from
Open

OCPBUGS-56045: OLMv1: Update test bundles [release-4.19] #29836

wants to merge 1 commit into from
+4 −4

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented May 21, 2025

These images are in both 4.18 and 4.19 catalogs

@tmshort
OLMv1: Update test bundles
5fecb7b 
These images are in both 4.18 and 4.19 catalogs

Signed-off-by: Todd Short <[email protected]>
@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 May 21, 2025
@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-56045, which is invalid:

  • expected dependent Jira Issue OCPBUGS-56047 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST 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.

In response to this:

These images are in both 4.18 and 4.19 catalogs

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.

@tmshort tmshort changed the title OCPBUGS-56045: OLMv1: Update test bundles OCPBUGS-56045: OLMv1: Update test bundles [release-4.19] May 21, 2025
@openshift-ci openshift-ci bot requested review from dinhxuanvu and sjenning May 21, 2025 16:14
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 21, 2025

@tmshort: 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/e2e-aws-ovn-fips 5fecb7b link true /test e2e-aws-ovn-fips
ci/prow/e2e-vsphere-ovn-upi 5fecb7b link true /test e2e-vsphere-ovn-upi
ci/prow/e2e-aws-ovn-single-node 5fecb7b link false /test e2e-aws-ovn-single-node
ci/prow/e2e-metal-ipi-ovn-ipv6 5fecb7b link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/okd-scos-e2e-aws-ovn 5fecb7b link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-edge-zones 5fecb7b link true /test e2e-aws-ovn-edge-zones
ci/prow/e2e-openstack-ovn 5fecb7b link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-upgrade 5fecb7b link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn 5fecb7b link false /test e2e-metal-ipi-ovn
ci/prow/e2e-gcp-ovn 5fecb7b link true /test e2e-gcp-ovn
ci/prow/e2e-aws-ovn-cgroupsv2 5fecb7b link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-vsphere-ovn 5fecb7b link true /test e2e-vsphere-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview 5fecb7b link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview

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.

@oceanc80
Copy link

/label backport-risk-assessed

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 22, 2025

@oceanc80: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label backport-risk-assessed

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.

@tmshort
Copy link
Contributor Author

tmshort commented May 23, 2025

/jira refresh

@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 May 23, 2025
@openshift-ci-robot
Copy link

@tmshort: This pull request references Jira Issue OCPBUGS-56045, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-56047 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-56047 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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

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.

@tmshort
Copy link
Contributor Author

tmshort commented May 23, 2025

/retest-required

@neisw
Copy link
Contributor

neisw commented May 23, 2025

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 23, 2025
@neisw
Copy link
Contributor

neisw commented May 23, 2025

/label backport-risk-assessed

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 23, 2025

@neisw: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label backport-risk-assessed

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.

@joelanford
Copy link
Member

/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 May 23, 2025
@joelanford
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 23, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joelanford, neisw, tmshort

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

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

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

@sjenning sjenning Awaiting requested review from sjenning

Assignees

@dgoodwin dgoodwin

@adambkaplan adambkaplan

@sayan-biswas sayan-biswas

@kasturinarra kasturinarra

@Moebasim Moebasim

@jadhaj jadhaj

@pamoedom pamoedom

@prietyc123 prietyc123

@gangwgr gangwgr

@prabhapa prabhapa

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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.