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

TRT-1576: Fail if operator has Available=False unless in upgrade window #28735

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

DennisPeriquet
Copy link
Contributor

@DennisPeriquet DennisPeriquet commented Apr 23, 2024

For this test: [bz-%v] clusteroperator/%v should not change condition/Available]:

  • For non-upgrade jobs, fail when operator goes to Available=False
  • For upgrade-jobs, fail when operator goes to Available=False unless it's during an upgrade window and the condition lasts for less than 10 minutes.

Once the PR where storage operator stops reporting Available status merges, we can remove the exception for it.

@openshift-ci openshift-ci bot requested review from deads2k and soltysh April 23, 2024 11:25
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2024
@DennisPeriquet
Copy link
Contributor Author

/payload-job periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

This will see if my new exception allows the upgrade job to pass despite the single storage operator replica.

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

@DennisPeriquet: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/272b5a20-0187-11ef-95a0-20b3d6d376a7-0

@DennisPeriquet
Copy link
Contributor Author

/payload-job periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

retry because the last one didn't really run

Copy link
Contributor

openshift-ci bot commented Apr 23, 2024

@DennisPeriquet: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/61bc6960-0194-11ef-8313-791cce82a878-0

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 63d0936

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd IncompleteTests
Tests for this run (16) are below the historical average (536): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 3014822

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd IncompleteTests
Tests for this run (25) are below the historical average (531): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@DennisPeriquet DennisPeriquet changed the title DO NOT MERGE: See how many jobs fail with Degraded=True and Available=False DO NOT MERGE: See how many jobs fail with Available=False Apr 26, 2024
@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: d950634

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-csi High
[OLM][invariant] alert/KubePodNotReady should not be at or above info in ns/openshift-marketplace
This test has passed 100.00% of 25 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-gcp-ovn-csi'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade Medium
[OLM][invariant] alert/KubePodNotReady should not be at or above info in ns/openshift-marketplace
This test has passed 96.70% of 818 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-gcp-ovn-upgrade' 'periodic-ci-openshift-release-master-ci-4.16-e2e-gcp-ovn-upgrade'] in the last 14 days.

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 2e4493a

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade High
[sig-apps] job-upgrade
This test has passed 100.00% of 32 runs on jobs ['periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-upgrade'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial Low
[bz-apiserver-auth] clusteroperator/authentication should not change condition/Available
This test has passed 0.00% of 62 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

Open Bugs
Single short-lived operand blip shouldn't cause authentication operator Available=False
---
[bz-Storage] clusteroperator/storage should not change condition/Available
This test has passed 0.00% of 62 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

Open Bugs
Setup new vsphere informing job
---
[sig-arch] events should not repeat pathologically for ns/openshift-etcd-operator
This test has passed 51.61% of 62 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
[bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver should not change condition/Available
This test has passed 1.61% of 62 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
Showing 4 of 12 test results

@DennisPeriquet
Copy link
Contributor Author

/test unit

@DennisPeriquet
Copy link
Contributor Author

/payload-job periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

Copy link
Contributor

openshift-ci bot commented Apr 29, 2024

@DennisPeriquet: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8a3d2950-0627-11ef-99cb-168bfde7d9b7-0

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 80a02e7

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade High
[sig-apps] job-upgrade
This test has passed 100.00% of 23 runs on jobs ['periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-upgrade'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial Low
[bz-Storage] clusteroperator/storage should not change condition/Available
This test has passed 0.00% of 45 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

Open Bugs
Setup new vsphere informing job
---
[bz-Routing] clusteroperator/ingress should not change condition/Available
This test has passed 0.00% of 45 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
[bz-Image Registry] clusteroperator/image-registry should not change condition/Available
This test has passed 22.22% of 45 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.

Open Bugs
CI: fail update suite if any ClusterOperator go Available=False outside of updates
---
[bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver should not change condition/Available
This test has passed 2.22% of 45 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
Showing 4 of 11 test results

@DennisPeriquet
Copy link
Contributor Author

/test unit

@DennisPeriquet
Copy link
Contributor Author

/payload-job periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

Copy link
Contributor

openshift-ci bot commented Apr 30, 2024

@DennisPeriquet: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.16-e2e-vsphere-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/6ff37c20-0690-11ef-86e4-c1c128b91d20-0

@DennisPeriquet DennisPeriquet changed the title DO NOT MERGE: See how many jobs fail with Available=False TRT-1576: Fail if operator has Available=False unless in upgrade window Apr 30, 2024
@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 30, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 30, 2024

@DennisPeriquet: This pull request references TRT-1576 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.16.0" version, but no target version was set.

In response to this:

Fail the [bz-%v] clusteroperator/%v should not change condition/Available] test for operators when Available=False outside of any upgrade window.

Add an exception for storage operator since it has only one replica.

This will give me a list of failures to look into. From the list of failures, we can see if there are already Jiras and decide if we want to add exceptions. Then, we'll update the PR with exceptions.

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

openshift-ci-robot commented Apr 30, 2024

@DennisPeriquet: This pull request references TRT-1576 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.16.0" version, but no target version was set.

In response to this:

For this test: [bz-%v] clusteroperator/%v should not change condition/Available]:

  • For non-upgrade jobs, fail when operator goes to Available=False
  • For upgrade-jobs, fail when operator goes to Available=False unless it's during an upgrade window and the condition lasts for less than 10 minutes.

Once the PR where storage operator stops reporting Available status merges, we can remove the exception for it.

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-trt-bot
Copy link

Job Failure Risk Analysis for sha: efde445

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade Low
[bz-kube-storage-version-migrator] clusteroperator/kube-storage-version-migrator should not change condition/Available
This test has passed 61.54% of 52 runs on jobs ['periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-upgrade'] in the last 14 days.
---
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Available
This test has passed 61.54% of 52 runs on jobs ['periodic-ci-openshift-release-master-ci-4.16-e2e-aws-ovn-upgrade'] in the last 14 days.

Open Bugs
control-plane-machine-set goes Available=False with UnavailableReplicas during updates

@DennisPeriquet
Copy link
Contributor Author

/test e2e-agnostic-ovn-cmd

@DennisPeriquet
Copy link
Contributor Author

/test verify

@DennisPeriquet
Copy link
Contributor Author

The single node serial test failed -- but not due to Available=False condition.

/test e2e-aws-ovn-single-node-serial

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 0e5fe19

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial IncompleteTests
Tests for this run (98) are below the historical average (877): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@DennisPeriquet
Copy link
Contributor Author

/test e2e-aws-ovn-single-node-serial

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 438d839

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade High
pull-ci-openshift-origin-master-e2e-gcp-csi High
External Storage [Driver: pd.csi.storage.gke.io] [Testpattern: Dynamic Snapshot (delete policy)] snapshottable [Feature:VolumeSnapshotDataSource] volume snapshot controller should check snapshot fields, check restore correctly works after modifying source data, check deletion (persistent)
This test has passed 100.00% of 20 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-gcp-ovn-csi'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2572): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1956): 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-master-e2e-aws-ovn-single-node-serial Low
[bz-openshift-apiserver] clusteroperator/openshift-apiserver should not change condition/Available
This test has passed 0.00% of 28 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
[bz-Management Console] clusteroperator/console should not change condition/Available
This test has passed 21.43% of 28 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
[bz-Storage] clusteroperator/csi-snapshot-controller should not change condition/Available
This test has passed 0.00% of 28 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
[bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver should not change condition/Available
This test has passed 0.00% of 28 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-serial'] in the last 14 days.
---
Showing 4 of 11 test results

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 0af0106

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-serial High
[Jira:"Cluster Version Operator"] monitor test legacy-cvo-invariants test evaluation
This test has passed 100.00% of 22 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-ci-4.17-e2e-aws-ovn-serial'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2547): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1936): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 0af0106

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2547): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1936): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@DennisPeriquet
Copy link
Contributor Author

/test verify

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 1ca0dc4

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2522): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1915): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

1 similar comment
@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 1ca0dc4

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2522): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1915): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@DennisPeriquet DennisPeriquet force-pushed the excepted_failures1 branch 2 times, most recently from 9fd1417 to 52d2c01 Compare May 17, 2024 19:10
@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 52d2c01

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2482): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1881): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

1 similar comment
@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 52d2c01

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2482): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1881): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@DennisPeriquet
Copy link
Contributor Author

/test e2e-aws-ovn-edge-zones

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 52d2c01

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2409): 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-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1867): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 97f3a73

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2364): 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-master-e2e-aws-ovn-cgroupsv2 IncompleteTests
Tests for this run (95) are below the historical average (2159): 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-master-e2e-aws-ovn-single-node Medium
[sig-node] static pods should start after being created
This test has passed 96.97% of 33 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node'] in the last 14 days.

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 97f3a73

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2364): 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-master-e2e-aws-ovn-cgroupsv2 IncompleteTests
Tests for this run (95) are below the historical average (2159): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@DennisPeriquet
Copy link
Contributor Author

/test e2e-aws-ovn-edge-zones
/test e2e-metal-ipi-ovn-ipv6

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 97f3a73

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (99) are below the historical average (2113): 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-master-e2e-aws-ovn-cgroupsv2 IncompleteTests
Tests for this run (95) are below the historical average (2143): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

// For the non-upgrade case, if any operator has Available=False, fail the test.
if condition.Type == configv1.OperatorAvailable {

// We'll add an exception for single node for now.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confusing comment I think, says we're adding an exception but we don't actually return the exception, we return empty string and nil which appears to actually mean no exception. I think we then trigger the degraded=True message below as the exception, which isn't even accurate for Available=false.

I would suggest something like:

if condition.Type == configv1.OperatorAvailable && condition.Status == configv1.ConditionFalse {

			// We'll add an exception for single node for now.
                        if isSingleNode {
                               return "Operators are allowed to go degraded on single-node for now", nil 
                       }
			return "", nil
		}

func isSingleNodeCheck(clientConfig *rest.Config) (bool, error) {
configClient, err := clientconfigv1.NewForConfig(clientConfig)
if err != nil {
logrus.Warnf("Error creating config client to check for Single Node configuration: %v", err)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

log.WithError(err).Error()

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 556ee0a

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade High
[sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator
This test has passed 99.42% of 3946 runs on release 4.17 [Overall] in the last week.
---
[bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available
This test has passed 99.42% of 3953 runs on release 4.17 [Overall] in the last week.

@DennisPeriquet
Copy link
Contributor Author

e2e-gcp-ovn test failure tracked in https://issues.redhat.com/browse/TRT-1680

@DennisPeriquet
Copy link
Contributor Author

/test e2e-aws-ovn-single-node-upgrade
/test e2e-gcp-ovn

Copy link
Contributor

openshift-ci bot commented May 23, 2024

@DennisPeriquet: 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-metal-ipi-sdn 97f3a73 link false /test e2e-metal-ipi-sdn
ci/prow/e2e-aws-ovn-single-node-upgrade 556ee0a link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node 556ee0a link false /test e2e-aws-ovn-single-node
ci/prow/e2e-gcp-ovn 556ee0a link true /test e2e-gcp-ovn

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.

@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 556ee0a

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-ovn Medium
[sig-storage] PersistentVolumes GCEPD [Feature:StorageProvider] should test that deleting the PV before the pod does not cause pod deletion to fail on PD detach [Skipped:NoOptionalCapabilities] [Suite:openshift/conformance/parallel] [Suite:k8s]
This test has passed 93.09% of 680 runs on release 4.17 [Overall] in the last week.

Open Bugs
4.17 ci failures: persistentvolumes "gce-" is forbidden ... GCE PD ...disk is not found
---
[sig-storage] Multi-AZ Cluster Volumes should schedule pods in the same zones as statically provisioned PVs [Suite:openshift/conformance/parallel] [Suite:k8s]
This test has passed 91.18% of 680 runs on release 4.17 [Overall] in the last week.

1 similar comment
@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 556ee0a

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-ovn Medium
[sig-storage] PersistentVolumes GCEPD [Feature:StorageProvider] should test that deleting the PV before the pod does not cause pod deletion to fail on PD detach [Skipped:NoOptionalCapabilities] [Suite:openshift/conformance/parallel] [Suite:k8s]
This test has passed 93.09% of 680 runs on release 4.17 [Overall] in the last week.

Open Bugs
4.17 ci failures: persistentvolumes "gce-" is forbidden ... GCE PD ...disk is not found
---
[sig-storage] Multi-AZ Cluster Volumes should schedule pods in the same zones as statically provisioned PVs [Suite:openshift/conformance/parallel] [Suite:k8s]
This test has passed 91.18% of 680 runs on release 4.17 [Overall] in the last week.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants