Skip to content

OCPQE-23184: Support external cloud authentication providers #28774

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
sunzhaohua2 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

OCPQE-23184: Support external cloud authentication providers #28774

sunzhaohua2 wants to merge 2 commits into from

Conversation

@sunzhaohua2
Copy link
Contributor

@sunzhaohua2 sunzhaohua2 commented May 7, 2024 •
edited
Loading

This will add test about pulling image from ECR/GCR/ACR.
As we are not allowed to push an image to container registry in advance, based on discussion , in code we create registry and mirror image, after testing remove registry.

  • We will set up a minimal, publicly pullable image (for ease) somewhere outside of the CI cloud accounts
  • The test will create an ECR (or equivalent) repo, and mirror the image across
  • Test will setup cleanup to remove the repo
  • PCO pruner will be updated to clean repos if we miss it

Feature Epic https://issues.redhat.com/browse/OCPCLOUD-2379

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 7, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 7, 2024 •
edited by openshift-ci bot
Loading

@sunzhaohua2: This pull request references OCPCLOUD-2558 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 task to target the "4.16.0" version, but no target version was set.

In response to this:

Local test result:
AWS

$ ./openshift-tests run-test "[sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from ECR"
INFO[0000] Decoding provider                             clusterState="<nil>" discover=false dryRun=false func=DecodeProvider providerType=
 May  7 14:20:19.722: INFO: microshift-version configmap not found
 Running Suite: OpenShift e2e suite - /Users/sunzhaohua/go/src/github.com/openshift/origin
 =========================================================================================
 Random Seed: 1715062817 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from ECR
 github.com/openshift/origin/test/extended/kubelet_authentication_providers/kubelet_authentication_providers.go:17
   STEP: Creating a kubernetes client @ 05/07/24 14:20:20.62
 May  7 14:20:23.590: INFO: configPath is now "/var/folders/0m/7xwxpmks77n3dm5rr8x8g92r0000gn/T/configfile247212266"
 May  7 14:20:23.590: INFO: The user is now "e2e-test-kubelet-authentication-providers-t28tx-user"
 May  7 14:20:23.590: INFO: Creating project "e2e-test-kubelet-authentication-providers-t28tx"
 May  7 14:20:23.901: INFO: Waiting on permissions in project "e2e-test-kubelet-authentication-providers-t28tx" ...
 May  7 14:20:24.533: INFO: Waiting for ServiceAccount "default" to be provisioned...
 May  7 14:20:24.849: INFO: Waiting for ServiceAccount "deployer" to be provisioned...
 May  7 14:20:25.160: INFO: Waiting for ServiceAccount "builder" to be provisioned...
 May  7 14:20:25.469: INFO: Waiting for RoleBinding "system:image-pullers" to be provisioned...
 May  7 14:20:25.884: INFO: Waiting for RoleBinding "system:image-builders" to be provisioned...
 May  7 14:20:26.298: INFO: Waiting for RoleBinding "system:deployers" to be provisioned...
 May  7 14:20:27.177: INFO: Project "e2e-test-kubelet-authentication-providers-t28tx" has been fully provisioned.
 May  7 14:20:27.177: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/aws/kubeconfig get infrastructure cluster -o=jsonpath={.status.platformStatus.type}'
 May  7 14:20:27.948: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/aws/kubeconfig get infrastructure cluster -o=jsonpath={.status.platformStatus.aws.region}'
   STEP: Add the AmazonEC2ContainerRegistryReadOnly policy to the worker nodes @ 05/07/24 14:20:28.719
 May  7 14:20:28.720: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/aws/kubeconfig get infrastructure cluster -o=jsonpath={.status.infrastructureName}'
 May  7 14:20:29.482: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/aws/kubeconfig get secret/aws-creds -n kube-system -o json'
 May  7 14:20:30.239: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/aws/kubeconfig get infrastructure cluster -o=jsonpath={.status.platformStatus.aws.region}'
   STEP: Create a new app using the image on ECR @ 05/07/24 14:20:32.184
 May  7 14:20:32.184: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/aws/kubeconfig new-app --name=hello-ecr --image=301721915996.dkr.ecr.us-east-2.amazonaws.com/hello-ecr:latest --allow-missing-images -n e2e-test-kubelet-authentication-providers-t28tx'
 W0507 14:20:33.123096   62275 newapp.go:523] Could not find an image stream match for "301721915996.dkr.ecr.us-east-2.amazonaws.com/hello-ecr:latest". Make sure that a container image with that tag is available on the node for the deployment to succeed.
 --> Found container image 7af3297 (6 years old) from 301721915996.dkr.ecr.us-east-2.amazonaws.com for "301721915996.dkr.ecr.us-east-2.amazonaws.com/hello-ecr:latest"


 --> Creating resources ...
     deployment.apps "hello-ecr" created
     service "hello-ecr" created
 --> Success
     Application is not exposed. You can expose services to the outside world by executing one or more of the commands below:
      'oc expose service/hello-ecr' 
     Run 'oc status' to view your app.
   STEP: Wait the pod to be running @ 05/07/24 14:20:33.575
 May  7 14:20:48.282: INFO: Deleted {user.openshift.io/v1, Resource=users  e2e-test-kubelet-authentication-providers-t28tx-user}, err: <nil>
 May  7 14:20:48.495: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-kubelet-authentication-providers-t28tx}, err: <nil>
 May  7 14:20:48.707: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~YD4cCjytD1tSyKCjlOcCEjUjTURQsbFa6xubRN4Frvg}, err: <nil>
   STEP: Destroying namespace "e2e-test-kubelet-authentication-providers-t28tx" for this suite. @ 05/07/24 14:20:48.708
 • [28.306 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 28.306 seconds

GCP

$ ./openshift-tests run-test "[sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from GCR"
INFO[0000] Decoding provider                             clusterState="<nil>" discover=false dryRun=false func=DecodeProvider providerType=
 May  7 14:18:15.334: INFO: Fetching cloud provider for "gce"
 I0507 14:18:15.338631   62120 gce.go:937] Using DefaultTokenSource &google.errWrappingTokenSource{src:(*oauth2.reuseTokenSource)(0xc001946ab0)}
 W0507 14:18:15.710738   62120 gce.go:491] No network name or URL specified.
 I0507 14:18:15.710827   62120 gce.go:512] managing multiple zones: [us-central1-a us-central1-b us-central1-c]
 May  7 14:18:15.930: INFO: microshift-version configmap not found
 Running Suite: OpenShift e2e suite - /Users/sunzhaohua/go/src/github.com/openshift/origin
 =========================================================================================
 Random Seed: 1715062684 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from GCR
 github.com/openshift/origin/test/extended/kubelet_authentication_providers/kubelet_authentication_providers.go:49
   STEP: Creating a kubernetes client @ 05/07/24 14:18:16.801
 May  7 14:18:31.986: INFO: configPath is now "/var/folders/0m/7xwxpmks77n3dm5rr8x8g92r0000gn/T/configfile2520542568"
 May  7 14:18:31.986: INFO: The user is now "e2e-test-kubelet-authentication-providers-vnrqj-user"
 May  7 14:18:31.986: INFO: Creating project "e2e-test-kubelet-authentication-providers-vnrqj"
 May  7 14:18:32.288: INFO: Waiting on permissions in project "e2e-test-kubelet-authentication-providers-vnrqj" ...
 May  7 14:18:33.042: INFO: Waiting for ServiceAccount "default" to be provisioned...
 May  7 14:18:33.358: INFO: Waiting for ServiceAccount "deployer" to be provisioned...
 May  7 14:18:33.678: INFO: Waiting for ServiceAccount "builder" to be provisioned...
 May  7 14:18:33.996: INFO: Waiting for RoleBinding "system:image-pullers" to be provisioned...
 May  7 14:18:34.681: INFO: Waiting for RoleBinding "system:image-builders" to be provisioned...
 May  7 14:18:35.111: INFO: Waiting for RoleBinding "system:deployers" to be provisioned...
 May  7 14:18:36.257: INFO: Project "e2e-test-kubelet-authentication-providers-vnrqj" has been fully provisioned.
 May  7 14:18:36.262: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/gcp/kubeconfig get infrastructure cluster -o=jsonpath={.status.platformStatus.type}'
   STEP: Create a new app using the image on GCR @ 05/07/24 14:18:37.17
 May  7 14:18:37.170: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/gcp/kubeconfig new-app --name=hello-gcr --image=gcr.io/openshift-qe/hello-gcr:latest --allow-missing-images -n e2e-test-kubelet-authentication-providers-vnrqj'
 W0507 14:18:38.294544   62139 newapp.go:523] Could not find an image stream match for "gcr.io/openshift-qe/hello-gcr:latest". Make sure that a container image with that tag is available on the node for the deployment to succeed.
 --> Found container image 7af3297 (6 years old) from gcr.io for "gcr.io/openshift-qe/hello-gcr:latest"


 --> Creating resources ...
     deployment.apps "hello-gcr" created
     service "hello-gcr" created
 --> Success
     Application is not exposed. You can expose services to the outside world by executing one or more of the commands below:
      'oc expose service/hello-gcr' 
     Run 'oc status' to view your app.
   STEP: Wait the pod to be running @ 05/07/24 14:18:38.88
 May  7 14:18:41.333: INFO: Deleted {user.openshift.io/v1, Resource=users  e2e-test-kubelet-authentication-providers-vnrqj-user}, err: <nil>
 May  7 14:18:41.555: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-kubelet-authentication-providers-vnrqj}, err: <nil>
 May  7 14:18:42.770: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~8j4UO-61tJBnoRFZaQV4AhmpXPhjN0qbxx3vP5YRGL8}, err: <nil>
   STEP: Destroying namespace "e2e-test-kubelet-authentication-providers-vnrqj" for this suite. @ 05/07/24 14:18:42.771
 • [26.408 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 26.409 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

Azure

$ ./openshift-tests run-test "[sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from ACR"
INFO[0000] Decoding provider                             clusterState="<nil>" discover=false dryRun=false func=DecodeProvider providerType=
 May  7 14:14:50.515: INFO: microshift-version configmap not found
 Running Suite: OpenShift e2e suite - /Users/sunzhaohua/go/src/github.com/openshift/origin
 =========================================================================================
 Random Seed: 1715062487 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from ACR
 github.com/openshift/origin/test/extended/kubelet_authentication_providers/kubelet_authentication_providers.go:64
   STEP: Creating a kubernetes client @ 05/07/24 14:14:51.418
 May  7 14:14:55.477: INFO: configPath is now "/var/folders/0m/7xwxpmks77n3dm5rr8x8g92r0000gn/T/configfile2343691754"
 May  7 14:14:55.477: INFO: The user is now "e2e-test-kubelet-authentication-providers-mpvxd-user"
 May  7 14:14:55.477: INFO: Creating project "e2e-test-kubelet-authentication-providers-mpvxd"
 May  7 14:14:55.872: INFO: Waiting on permissions in project "e2e-test-kubelet-authentication-providers-mpvxd" ...
 May  7 14:14:56.778: INFO: Waiting for ServiceAccount "default" to be provisioned...
 May  7 14:14:57.164: INFO: Waiting for ServiceAccount "deployer" to be provisioned...
 May  7 14:14:57.553: INFO: Waiting for ServiceAccount "builder" to be provisioned...
 May  7 14:14:57.940: INFO: Waiting for RoleBinding "system:image-pullers" to be provisioned...
 May  7 14:14:58.506: INFO: Waiting for RoleBinding "system:image-builders" to be provisioned...
 May  7 14:14:59.090: INFO: Waiting for RoleBinding "system:deployers" to be provisioned...
 May  7 14:15:00.284: INFO: Project "e2e-test-kubelet-authentication-providers-mpvxd" has been fully provisioned.
 May  7 14:15:00.289: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/azure/kubeconfig get infrastructure cluster -o=jsonpath={.status.platformStatus.type}'
 May  7 14:15:01.786: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/azure/kubeconfig get infrastructure cluster -o=jsonpath={.status.platformStatus.azure.cloudName}'
   STEP: Create RoleAssignments for resourcegroup @ 05/07/24 14:15:02.868
 May  7 14:15:02.868: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/azure/kubeconfig get infrastructure cluster -o=jsonpath={.status.infrastructureName}'
 May  7 14:15:04.245: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/azure/kubeconfig get secret/azure-credentials -n kube-system -o=jsonpath={.data}'
 May  7 14:15:05.233: INFO: Azure credentials successfully loaded.
 May  7 14:15:13.478: INFO: Role assignment created: 53b8f551-140d-438c-ba67-43fe172d538d
   STEP: Create a new app using the image on ACR @ 05/07/24 14:15:13.478
 May  7 14:15:13.478: INFO: Running 'oc --kubeconfig=/Users/sunzhaohua/kubeconfig/azure/kubeconfig new-app --name=hello-acr --image=zhsunregistry.azurecr.io/hello-acr:latest --allow-missing-images -n e2e-test-kubelet-authentication-providers-mpvxd'
 W0507 14:15:14.838662   61979 newapp.go:523] Could not find an image stream match for "zhsunregistry.azurecr.io/hello-acr:latest". Make sure that a container image with that tag is available on the node for the deployment to succeed.
 --> Found container image 7af3297 (6 years old) from zhsunregistry.azurecr.io for "zhsunregistry.azurecr.io/hello-acr:latest"


 --> Creating resources ...
     deployment.apps "hello-acr" created
     service "hello-acr" created
 --> Success
     Application is not exposed. You can expose services to the outside world by executing one or more of the commands below:
      'oc expose service/hello-acr' 
     Run 'oc status' to view your app.
   STEP: Wait the pod to be running @ 05/07/24 14:15:15.513
 May  7 14:15:17.205: INFO: Deleted {user.openshift.io/v1, Resource=users  e2e-test-kubelet-authentication-providers-mpvxd-user}, err: <nil>
 May  7 14:15:17.472: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-kubelet-authentication-providers-mpvxd}, err: <nil>
 May  7 14:15:17.742: INFO: Deleted {oauth.openshift.io/v1, Resource=oauthaccesstokens  sha256~gjXih-PLLeHKO3vfK2jiSXQUMXm4Eh4zEtIfbNv0iMM}, err: <nil>
   STEP: Destroying namespace "e2e-test-kubelet-authentication-providers-mpvxd" for this suite. @ 05/07/24 14:15:17.743
 • [26.603 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 26.603 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 7, 2024
@openshift-ci openshift-ci bot requested review from sjenning and soltysh May 7, 2024 06:29
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label May 7, 2024
JoelSpeed
JoelSpeed reviewed May 7, 2024
View reviewed changes
@JoelSpeed
Copy link
Contributor

JoelSpeed commented May 7, 2024

I can't see the new tests in the JUnit output, are they showing for you?

@sunzhaohua2
Copy link
Contributor Author

sunzhaohua2 commented May 7, 2024

I can't see the new tests in the JUnit output, are they showing for you?

Seems need to run make update so that test/extended/util/annotate/generated/zz_generated.annotations.go can be updated, now I can see

$ ./openshift-tests run --dry-run "openshift/conformance/serial" | grep -E KubeletAuthenticationProviders    
INFO[0000] Decoding provider                             clusterState="<nil>" discover=true dryRun=true func=DecodeProvider providerType=
"[sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from ACR [Suite:openshift/conformance/serial]"
"[sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from ECR [Suite:openshift/conformance/serial]"
"[sig-cluster-lifecycle][Feature:KubeletAuthenticationProviders][Serial] KubeletAuthenticationProviders should should be able to pull images from GCR [Suite:openshift/conformance/serial]"

@JoelSpeed
Copy link
Contributor

JoelSpeed commented May 7, 2024

Great, can see now that the test is failing, so lets try to get the images uploaded so we can get this to pass, thanks!

@sunzhaohua2
Copy link
Contributor Author

sunzhaohua2 commented May 8, 2024

Great, can see now that the test is failing, so lets try to get the images uploaded so we can get this to pass, thanks!

asked here https://redhat-internal.slack.com/archives/CBN38N3MW/p1715133269211149

@sunzhaohua2 sunzhaohua2 force-pushed the private-image branch 2 times, most recently from cc5b585 to 52c34a9 Compare May 20, 2024 13:23
@openshift-trt-bot
Copy link

openshift-trt-bot commented May 20, 2024

Job Failure Risk Analysis for sha: 52c34a9

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 20, 2024

@sunzhaohua2: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-edge-zones
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-image-registry
  • /test e2e-aws-ovn-serial
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-builds
  • /test e2e-gcp-ovn-image-ecosystem
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-metal-ipi-ovn-ipv6
  • /test images
  • /test lint
  • /test unit
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-etcd-recovery
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-etcd-scaling
  • /test e2e-aws-ovn-kubevirt
  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-ovn-single-node-serial
  • /test e2e-aws-ovn-single-node-upgrade
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-upi
  • /test e2e-aws-proxy
  • /test e2e-azure
  • /test e2e-azure-ovn-etcd-scaling
  • /test e2e-azure-ovn-upgrade
  • /test e2e-baremetalds-kubevirt
  • /test e2e-gcp-csi
  • /test e2e-gcp-disruptive
  • /test e2e-gcp-fips-serial
  • /test e2e-gcp-ovn-etcd-scaling
  • /test e2e-gcp-ovn-rt-upgrade
  • /test e2e-gcp-ovn-techpreview
  • /test e2e-gcp-ovn-techpreview-serial
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-dualstack-local-gateway
  • /test e2e-metal-ipi-sdn
  • /test e2e-metal-ipi-serial
  • /test e2e-metal-ipi-serial-ovn-ipv6
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-openstack-ovn
  • /test e2e-openstack-serial
  • /test e2e-vsphere
  • /test e2e-vsphere-ovn-dualstack-primaryv6
  • /test e2e-vsphere-ovn-etcd-scaling
  • /test okd-e2e-gcp
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-origin-master-e2e-aws-csi
  • pull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones
  • pull-ci-openshift-origin-master-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-master-e2e-aws-ovn-serial
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade
  • pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-origin-master-e2e-gcp-csi
  • pull-ci-openshift-origin-master-e2e-gcp-ovn
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-builds
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-master-e2e-metal-ipi-sdn
  • pull-ci-openshift-origin-master-e2e-openstack-ovn
  • pull-ci-openshift-origin-master-images
  • pull-ci-openshift-origin-master-lint
  • pull-ci-openshift-origin-master-unit
  • pull-ci-openshift-origin-master-verify
  • pull-ci-openshift-origin-master-verify-deps

In response to this:

/test e2e-azure-ovn-serial

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.

@openshift-trt-bot
Copy link

openshift-trt-bot commented May 21, 2024

Job Failure Risk Analysis for sha: ea95b62

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade High
[bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available
This test has passed 99.60% of 3458 runs on release 4.17 [Overall] in the last week.
---
[sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator
This test has passed 99.57% of 3454 runs on release 4.17 [Overall] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial IncompleteTests
Tests for this run (98) are below the historical average (770): 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 (1617): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 21, 2024

@sunzhaohua2: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-jenkins
  • /test e2e-aws-ovn-edge-zones
  • /test e2e-aws-ovn-fips
  • /test e2e-aws-ovn-image-registry
  • /test e2e-aws-ovn-serial
  • /test e2e-gcp-ovn
  • /test e2e-gcp-ovn-builds
  • /test e2e-gcp-ovn-image-ecosystem
  • /test e2e-gcp-ovn-upgrade
  • /test e2e-metal-ipi-ovn-ipv6
  • /test images
  • /test lint
  • /test unit
  • /test verify
  • /test verify-deps

The following commands are available to trigger optional jobs:

  • /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
  • /test e2e-agnostic-ovn-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-disruptive
  • /test e2e-aws-etcd-recovery
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-cgroupsv2
  • /test e2e-aws-ovn-etcd-scaling
  • /test e2e-aws-ovn-kubevirt
  • /test e2e-aws-ovn-single-node
  • /test e2e-aws-ovn-single-node-serial
  • /test e2e-aws-ovn-single-node-upgrade
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-upi
  • /test e2e-aws-proxy
  • /test e2e-azure
  • /test e2e-azure-ovn-etcd-scaling
  • /test e2e-azure-ovn-upgrade
  • /test e2e-baremetalds-kubevirt
  • /test e2e-gcp-csi
  • /test e2e-gcp-disruptive
  • /test e2e-gcp-fips-serial
  • /test e2e-gcp-ovn-etcd-scaling
  • /test e2e-gcp-ovn-rt-upgrade
  • /test e2e-gcp-ovn-techpreview
  • /test e2e-gcp-ovn-techpreview-serial
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-dualstack-local-gateway
  • /test e2e-metal-ipi-sdn
  • /test e2e-metal-ipi-serial
  • /test e2e-metal-ipi-serial-ovn-ipv6
  • /test e2e-metal-ipi-virtualmedia
  • /test e2e-openstack-ovn
  • /test e2e-openstack-serial
  • /test e2e-vsphere
  • /test e2e-vsphere-ovn-dualstack-primaryv6
  • /test e2e-vsphere-ovn-etcd-scaling
  • /test okd-e2e-gcp
  • /test okd-scos-images

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-origin-master-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-origin-master-e2e-aws-csi
  • pull-ci-openshift-origin-master-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones
  • pull-ci-openshift-origin-master-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-master-e2e-aws-ovn-serial
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-serial
  • pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade
  • pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-origin-master-e2e-gcp-csi
  • pull-ci-openshift-origin-master-e2e-gcp-ovn
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-builds
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-master-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-master-e2e-metal-ipi-sdn
  • pull-ci-openshift-origin-master-e2e-openstack-ovn
  • pull-ci-openshift-origin-master-images
  • pull-ci-openshift-origin-master-lint
  • pull-ci-openshift-origin-master-unit
  • pull-ci-openshift-origin-master-verify
  • pull-ci-openshift-origin-master-verify-deps

In response to this:

/test e2e-azure-fips-serial

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.

@JoelSpeed
Copy link
Contributor

JoelSpeed commented May 21, 2024

/payload-job periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 21, 2024

@JoelSpeed: 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.17-e2e-azure-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/06908cd0-174a-11ef-9adf-a5c46a74c547-0

@openshift-trt-bot
Copy link

openshift-trt-bot commented May 21, 2024

Job Failure Risk Analysis for sha: 8f4fa63

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade High
[bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available
This test has passed 99.59% of 3384 runs on release 4.17 [Overall] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1598): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@sunzhaohua2
Copy link
Contributor Author

sunzhaohua2 commented May 22, 2024

/payload-job periodic-ci-openshift-release-master-nightly-4.17-e2e-gcp-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 22, 2024

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

  • periodic-ci-openshift-release-master-nightly-4.17-e2e-gcp-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2b85aa90-17e3-11ef-8a5a-54c02cf856df-0

@openshift-trt-bot
Copy link

openshift-trt-bot commented May 22, 2024

Job Failure Risk Analysis for sha: 7e362f5

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade High
[bz-Node Tuning Operator] clusteroperator/node-tuning should not change condition/Available
This test has passed 99.63% of 3780 runs on release 4.17 [Overall] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node IncompleteTests
Tests for this run (98) are below the historical average (1551): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@sunzhaohua2
Copy link
Contributor Author

sunzhaohua2 commented May 22, 2024

/payload-job periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 22, 2024

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

  • periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9e14bdf0-1804-11ef-8b77-f885f8f851e4-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 6, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JoelSpeed, sunzhaohua2
Once this PR has been reviewed and has the lgtm label, please ask for approval from deads2k. For more information see the Kubernetes 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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 7, 2024 •
edited by openshift-ci bot
Loading

@sunzhaohua2: This pull request references OCPQE-23184 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 task to target the "4.17.0" version, but no target version was set.

In response to this:

This will add test about pulling image from ECR/GCR/ACR.
As we are not allowed to push an image to container registry in advance, based on discussion , in code we create registry and mirror image, after testing remove registry.

  • We will set up a minimal, publicly pullable image (for ease) somewhere outside of the CI cloud accounts
  • The test will create an ECR (or equivalent) repo, and mirror the image across
  • Test will setup cleanup to remove the repo
  • PCO pruner will be updated to clean repos if we miss it

Feature Epic https://issues.redhat.com/browse/OCPCLOUD-2379

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

openshift-trt-bot commented Aug 7, 2024

Job Failure Risk Analysis for sha: 6498af5

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 98.48% of 66 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.
pull-ci-openshift-origin-master-e2e-aws-ovn-ipsec-serial High
operator conditions monitoring
This test has passed 100.00% of 58 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial' '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.

Open Bugs
vSphere installs failing due to machines stuck in Provisioned
pull-ci-openshift-origin-master-e2e-aws-ovn-upgrade Medium
[sig-network] pods should successfully create sandboxes by other
This test has passed 93.85% of 130 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade'] in the last 14 days.

@openshift-trt-bot
Copy link

openshift-trt-bot commented Aug 7, 2024

Job Failure Risk Analysis for sha: 6498af5

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-ipsec-serial High
operator conditions monitoring
This test has passed 100.00% of 59 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial' '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.

Open Bugs
vSphere installs failing due to machines stuck in Provisioned

@openshift-trt-bot
Copy link

openshift-trt-bot commented Aug 8, 2024

Job Failure Risk Analysis for sha: 6498af5

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 98.70% of 77 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

1 similar comment
@openshift-trt-bot
Copy link

openshift-trt-bot commented Aug 8, 2024

Job Failure Risk Analysis for sha: 6498af5

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 98.70% of 77 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

@sunzhaohua2 sunzhaohua2 requested a review from soltysh August 21, 2024 02:24
@openshift-trt-bot
Copy link

openshift-trt-bot commented Aug 21, 2024

Job Failure Risk Analysis for sha: 6498af5

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 100.00% of 153 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-kube-apiserver-rollout IncompleteTests
Tests for this run (20) are below the historical average (739): 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-kube-apiserver-rollout Low
[Conformance][Suite:openshift/kube-apiserver/rollout][Jira:"kube-apiserver"][sig-kube-apiserver] kube-apiserver should roll out new revisions without disruption [apigroup:config.openshift.io][apigroup:operator.openshift.io]
This test has passed 50.00% of 20 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-kube-apiserver-rollout' 'periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-kube-apiserver-rollout'] in the last 14 days.

@openshift-trt-bot
Copy link

openshift-trt-bot commented Aug 21, 2024

Job Failure Risk Analysis for sha: 6498af5

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 100.00% of 153 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-kube-apiserver-rollout IncompleteTests
Tests for this run (20) are below the historical average (739): 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

openshift-trt-bot commented Aug 28, 2024

Job Failure Risk Analysis for sha: 000f2ea

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-ipsec-serial High
[sig-arch] events should not repeat pathologically for ns/openshift-ovn-kubernetes
This test has passed 100.00% of 35 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days.

@openshift-trt-bot
Copy link

openshift-trt-bot commented Aug 29, 2024

Job Failure Risk Analysis for sha: 000f2ea

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-serial Medium
[sig-arch][Late] clients should not use APIs that are removed in upcoming releases [apigroup:apiserver.openshift.io] [Suite:openshift/conformance/parallel]
This test has passed 97.30% of 37 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days.

Open Bugs
Removed APIs are still used in some test environment

@sunzhaohua2
Copy link
Contributor Author

sunzhaohua2 commented Nov 29, 2024

/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 29, 2024

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

  • periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f9ae2580-ae49-11ef-9981-e8bff0cb2942-0

@sunzhaohua2
Copy link
Contributor Author

sunzhaohua2 commented Nov 29, 2024

/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 29, 2024

@sunzhaohua2: 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.18-e2e-azure-ovn-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fe7bb320-ae49-11ef-8ee2-744f3b3e7bc0-0

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 12, 2025
@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Feb 12, 2025

PR needs rebase.

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.

@openshift-trt
Copy link

openshift-trt bot commented Feb 12, 2025

Job Failure Risk Analysis for sha: 687d4ea

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-ovn-builds High

@openshift-trt
Copy link

openshift-trt bot commented May 28, 2025

Job Failure Risk Analysis for sha: 687d4ea

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2 IncompleteTests
Tests for this run (2) are below the historical average (1999): 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-2of2 IncompleteTests
Tests for this run (2) are below the historical average (1969): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-bot
Copy link
Contributor

openshift-bot commented Aug 27, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 27, 2025
@openshift-bot
Copy link
Contributor

openshift-bot commented Sep 27, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 27, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@sunzhaohua2: 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-ipsec-serial 000f2ea link false /test e2e-aws-ovn-ipsec-serial
ci/prow/e2e-aws-ovn-single-node-serial 000f2ea link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-builds 000f2ea link true /test e2e-gcp-ovn-builds
ci/prow/okd-scos-images 687d4ea link true /test okd-scos-images
ci/prow/e2e-vsphere-ovn 687d4ea link true /test e2e-vsphere-ovn
ci/prow/verify-deps 687d4ea link true /test verify-deps
ci/prow/e2e-aws-ovn-serial 687d4ea link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-fips 687d4ea link true /test e2e-aws-ovn-fips
ci/prow/verify 687d4ea link true /test verify
ci/prow/images 687d4ea link true /test images
ci/prow/unit 687d4ea link true /test unit
ci/prow/e2e-gcp-ovn-upgrade 687d4ea link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-vsphere-ovn-upi 687d4ea link true /test e2e-vsphere-ovn-upi
ci/prow/e2e-gcp-ovn 687d4ea link true /test e2e-gcp-ovn
ci/prow/e2e-aws-ovn-edge-zones 687d4ea link true /test e2e-aws-ovn-edge-zones
ci/prow/lint 687d4ea link true /test lint
ci/prow/e2e-aws-ovn-serial-1of2 687d4ea link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-ovn-serial-2of2 687d4ea link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-gcp-csi 687d4ea link true /test e2e-gcp-csi
ci/prow/e2e-aws-csi 687d4ea link true /test e2e-aws-csi
ci/prow/go-verify-deps 687d4ea link true /test go-verify-deps
ci/prow/e2e-aws-ovn-microshift-serial 687d4ea link true /test e2e-aws-ovn-microshift-serial
ci/prow/e2e-aws-ovn-microshift 687d4ea link true /test e2e-aws-ovn-microshift
ci/prow/e2e-metal-ipi-ovn-ipv6 687d4ea link true /test e2e-metal-ipi-ovn-ipv6

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.

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

Reviewers

@JoelSpeed JoelSpeed JoelSpeed left review comments

@sjenning sjenning Awaiting requested review from sjenning

@soltysh soltysh Awaiting requested review from soltysh

Assignees

@soltysh soltysh

@deads2k deads2k

@JoelSpeed JoelSpeed

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

10 participants

@sunzhaohua2 @openshift-ci-robot @JoelSpeed @openshift-trt-bot @jupierce @miyadav @openshift-merge-robot @openshift-bot @soltysh @deads2k