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

Ensure OS environment variables are wired into list command as well #29582

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

Conversation

stbenjam
Copy link
Member

@stbenjam stbenjam commented Mar 6, 2025

When getting the list of tests, we need to have origin's environment variables.

Some users are setting TEST_PROVIDER when invoking openshift-tests, which for run this gets overwritten with the correct ones from the cluster environment[1], but this doesn't happen with list.

An upcoming change is going to require initializing the test framework even to list tests, which means we'll need to have the TEST_PROVIDER correctly set.

[1] https://github.com/openshift/origin/blob/main/pkg/test/ginkgo/test_runner.go#L380-L403

@openshift-ci openshift-ci bot requested review from deads2k and p0lyn0mial March 6, 2025 13:49
Copy link
Contributor

openshift-ci bot commented Mar 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stbenjam

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 Mar 6, 2025
When getting the list of tests, we need to have origin's environment
variables.

Some users are setting TEST_PROVIDER when invoking openshift-tests,
which for `run` this gets overwritten with the correct ones from the
cluster environment[1], but this doesn't happen with `list`.

An upcoming change is going to require initializing the test framework
even to list tests, which means we'll need to have the TEST_PROVIDER
correctly set.

[1] https://github.com/openshift/origin/blob/main/pkg/test/ginkgo/test_runner.go#L380-L403
@stbenjam stbenjam force-pushed the update-env-vars-list-test branch from c1ddb97 to 0055a0b Compare March 6, 2025 18:27
Copy link
Contributor

openshift-ci bot commented Mar 7, 2025

@stbenjam: 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-gcp-ovn-upgrade 0055a0b link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 0055a0b link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn 0055a0b link true /test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-virtualmedia 0055a0b link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-gcp-csi 0055a0b link false /test e2e-gcp-csi
ci/prow/e2e-aws-ovn-single-node-serial 0055a0b link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-rt-upgrade 0055a0b link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback 0055a0b link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-ovn-etcd-scaling 0055a0b link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-ovn-etcd-scaling 0055a0b link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-microshift 0055a0b link true /test e2e-aws-ovn-microshift
ci/prow/e2e-metal-ipi-ovn-dualstack 0055a0b link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-openstack-ovn 0055a0b link false /test e2e-openstack-ovn
ci/prow/e2e-agnostic-ovn-cmd 0055a0b link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-openstack-serial 0055a0b link false /test e2e-openstack-serial
ci/prow/e2e-aws-ovn-fips 0055a0b link true /test e2e-aws-ovn-fips
ci/prow/e2e-metal-ipi-ovn 0055a0b link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-cgroupsv2 0055a0b link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 0055a0b link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-hypershift-conformance 0055a0b link false /test e2e-hypershift-conformance
ci/prow/e2e-aws-ovn-serial 0055a0b link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-upgrade 0055a0b link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws 0055a0b link false /test e2e-aws
ci/prow/e2e-aws-ovn-single-node 0055a0b link false /test e2e-aws-ovn-single-node
ci/prow/e2e-azure-ovn-upgrade 0055a0b link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-gcp-disruptive 0055a0b link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-ovn-microshift-serial 0055a0b link true /test e2e-aws-ovn-microshift-serial
ci/prow/e2e-vsphere-ovn-etcd-scaling 0055a0b link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-aws-proxy 0055a0b link false /test e2e-aws-proxy
ci/prow/e2e-aws-disruptive 0055a0b link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 0055a0b link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn 0055a0b link false /test e2e-aws-ovn
ci/prow/e2e-aws-ovn-edge-zones 0055a0b link true /test e2e-aws-ovn-edge-zones
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway 0055a0b link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-metal-ipi-ovn-ipv6 0055a0b link true /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-single-node-upgrade 0055a0b link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 0055a0b link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-vsphere-ovn-upi 0055a0b link true /test e2e-vsphere-ovn-upi
ci/prow/e2e-metal-ipi-serial 0055a0b link false /test e2e-metal-ipi-serial
ci/prow/e2e-gcp-fips-serial 0055a0b link false /test e2e-gcp-fips-serial
ci/prow/okd-e2e-gcp 0055a0b link false /test okd-e2e-gcp
ci/prow/e2e-vsphere-ovn 0055a0b link true /test e2e-vsphere-ovn
ci/prow/e2e-azure 0055a0b link false /test e2e-azure
ci/prow/e2e-azure-ovn-etcd-scaling 0055a0b link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-csi 0055a0b link false /test e2e-aws-csi
ci/prow/okd-scos-e2e-aws-ovn 0055a0b link false /test okd-scos-e2e-aws-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.

Copy link

openshift-trt bot commented Mar 7, 2025

Job Failure Risk Analysis for sha: 0055a0b

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-agnostic-ovn-cmd IncompleteTests
Tests for this run (106) are below the historical average (1217): 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 IncompleteTests
Tests for this run (105) are below the historical average (2894): 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-csi IncompleteTests
Tests for this run (105) are below the historical average (1483): 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 IncompleteTests
Tests for this run (105) are below the historical average (1400): 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-ovn IncompleteTests
Tests for this run (105) are below the historical average (3129): 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-ovn-cgroupsv2 IncompleteTests
Tests for this run (105) are below the historical average (2890): 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-ovn-edge-zones IncompleteTests
Tests for this run (107) are below the historical average (1389): 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-ovn-etcd-scaling IncompleteTests
Tests for this run (105) are below the historical average (1665): 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-ovn-fips IncompleteTests
Tests for this run (105) are below the historical average (2080): 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-ovn-kube-apiserver-rollout IncompleteTests
Tests for this run (105) are below the historical average (1623): 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-ovn-microshift IncompleteTests
Tests for this run (24) are below the historical average (1049): 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-ovn-microshift-serial IncompleteTests
Tests for this run (24) are below the historical average (499): 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-ovn-serial IncompleteTests
Tests for this run (105) are below the historical average (1143): 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-ovn-single-node IncompleteTests
Tests for this run (105) are below the historical average (2352): 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-ovn-single-node-serial IncompleteTests
Tests for this run (105) are below the historical average (1542): 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-ovn-single-node-upgrade IncompleteTests
Tests for this run (106) are below the historical average (3404): 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-ovn-upgrade IncompleteTests
Tests for this run (107) are below the historical average (1652): 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-proxy IncompleteTests
Tests for this run (106) are below the historical average (3120): 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-azure IncompleteTests
Tests for this run (106) are below the historical average (2093): 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-azure-ovn-etcd-scaling IncompleteTests
Tests for this run (106) are below the historical average (1239): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

Showing 20 of 43 jobs analysis

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant