Description of problem: oVirt didn't get a chance to be added as a provider to Kubernetes e2e tests [1][2][3], So we need to be added to origin like IBM on [4]. This is needed for skipping tests for ovirt [5] [1] https://github.com/kubernetes-cn/kubernetes/blob/c3bec0bae43b4c46800a13f44534ce6cd14b5f40/test/e2e/framework/providers/openstack/openstack.go [2] https://github.com/kubernetes-cn/kubernetes/blob/c3bec0bae43b4c46800a13f44534ce6cd14b5f40/test/e2e/framework/providers/vsphere/vsphere.go [3] https://github.com/kubernetes-cn/kubernetes/blob/c3bec0bae43b4c46800a13f44534ce6cd14b5f40/test/e2e/framework/providers/azure/azure.go [4] https://github.com/openshift/origin/pull/24817 [5] https://github.com/openshift/origin/blob/master/cmd/openshift-tests/provider.go#L57-L63
Moving to unknown component, this is not under purview of DPTP. Is there actually anything QE needs to do here?
(In reply to Steve Kuznetsov from comment #4) > Moving to unknown component, this is not under purview of DPTP. Is there > actually anything QE needs to do here? No not really, tested locally and if there will be a problem we will see it on CI
(In reply to Steve Kuznetsov from comment #4) > Moving to unknown component, this is not under purview of DPTP. Is there > actually anything QE needs to do here? Can I move this to verified since QE doesn't need to do anything and I verified it locally? (I want to cherry-pick it to 4.5)
(In reply to Gal Zaidman from comment #6) > (In reply to Steve Kuznetsov from comment #4) > > Moving to unknown component, this is not under purview of DPTP. Is there > > actually anything QE needs to do here? > > Can I move this to verified since QE doesn't need to do anything and I > verified it locally? (I want to cherry-pick it to 4.5) Gal go ahead and do that. For the verification its enough that you prove the tests are skipped for ovirt now. (extract something from the ci job execution or similar)
Tested with quay.io/openshift/origin-tests:latest: [root@83b236ffecf5 /]# openshift-tests run openshift/conformance/parallel --dry-run --provider '{"type":"test"}' W0607 10:08:44.895931 90 test_context.go:414] Unable to find in-cluster config, using default host : http://127.0.0.1:8080 I0607 10:08:44.896051 90 test_context.go:423] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready E0607 10:08:44.896075 90 test_context.go:449] Unknown provider "test". The following providers are known: aws azure gce gke ibmcloud kubemark local openstack ovirt skeleton vsphere
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days