Skip to content
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.

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

OCPBUGS-22413: Add myql-80 to fix known image check test for OKD #29659

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Prashanth684
Copy link
Contributor

This issue was peviously reported and even fixed through #28357, but it was reverted by #28367. Instead of changing the images, add this image to the allowed list so the test doesn't flake

This issue was peviously reported and even fixed through
openshift#28357, but it was reverted by
openshift#28367. Instead of changing the
images, add this image to the allowed list so the test doesn't flake
@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 9, 2025
@openshift-ci-robot
Copy link

@Prashanth684: This pull request references Jira Issue OCPBUGS-22413, which is invalid:

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

This issue was peviously reported and even fixed through #28357, but it was reverted by #28367. Instead of changing the images, add this image to the allowed list so the test doesn't flake

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 9, 2025
@openshift-ci openshift-ci bot requested review from deads2k and sjenning April 9, 2025 05:31
Copy link
Contributor

openshift-ci bot commented Apr 9, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Prashanth684
Once this PR has been reviewed and has the lgtm label, please assign sosiouxme for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@Prashanth684
Copy link
Contributor Author

/retest-required

@Prashanth684
Copy link
Contributor Author

/retest

Copy link
Contributor

openshift-ci bot commented Apr 14, 2025

@Prashanth684: 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-etcd-scaling 7d32bbf link false /test e2e-aws-ovn-etcd-scaling
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback 7d32bbf link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview 7d32bbf link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-openstack-serial 7d32bbf link false /test e2e-openstack-serial
ci/prow/e2e-azure-ovn-etcd-scaling 7d32bbf link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-ovn-etcd-scaling 7d32bbf link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 7d32bbf link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-upgrade 7d32bbf link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-etcd-scaling 7d32bbf link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive 7d32bbf link false /test e2e-gcp-disruptive
ci/prow/okd-e2e-gcp 7d32bbf link false /test okd-e2e-gcp
ci/prow/e2e-aws-disruptive 7d32bbf link false /test e2e-aws-disruptive
ci/prow/okd-scos-e2e-aws-ovn 7d32bbf link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-fips-serial 7d32bbf link false /test e2e-gcp-fips-serial

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.

Copy link

openshift-trt bot commented Apr 14, 2025

Job Failure Risk Analysis for sha: 7d32bbf

Job Name Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback IncompleteTests
Tests for this run (88) are below the historical average (218): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-aws-disruptive Medium
[bz-Etcd] clusteroperator/etcd should not change condition/Available
Potential external regression detected for High Risk Test analysis
---
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis
---
[sig-node] node-lifecycle detects unexpected not ready node
Potential external regression detected for High Risk Test analysis

Open Bugs
[sig-node] node-lifecycle detects unexpected not ready node failing on azure serial and upgrade jobs
pull-ci-openshift-origin-main-okd-e2e-gcp IncompleteTests
Tests for this run (15) are below the historical average (28): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-okd-scos-e2e-aws-ovn IncompleteTests
Tests for this run (97) are below the historical average (2512): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants