Bug 2045590

Summary:	enable openshift conformance tests to work with AlibabaCloud clusters
Product:	OpenShift Container Platform	Reporter:	Kenny Woodson <kwoodson>
Component:	Test Framework	Assignee:	OpenShift Release Oversight <openshift-release-oversight>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-30 18:04:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2046002, 2058688

Description Kenny Woodson 2022-01-25 17:50:55 UTC

Description of problem:
While creating CI jobs for testing and creating AlibabaCloud clusters the process fails because platform is missing from the origin repository.

Version-Release number of selected component (if applicable):
4.10

How reproducible:
Always

Steps to Reproduce:
1. Run openshift-tests with --provider set to alibabacloud.
2.
3.

Actual results:
Current e2e tests fail with the current error message:

E0124 22:54:06.535535     281 test_context.go:503] Unknown provider "alibabacloud". The following providers are known: aws azure baremetal gce gke ibmcloud kubemark kubevirt local openstack ovirt skeleton vsphere

Expected results:
e2e conformance tests should run. Running this manually locally I was able to run the tests with a PR to add alibabacloud to the origin repository.



Writing JUnit report to junit/junit_e2e_20220125-171408.xml

error: 24 fail, 1105 pass, 1578 skip (37m1s)


Additional info:

Comment 5 Kenny Woodson 2022-02-21 13:38:03 UTC

Testing results:

10/3085 Tests Failed
14/3085 Tests Flaky
1365/3085 Tests Passed!
1696/3085 Tests Skipped.

Comment 7 Rory Thrasher 2024-04-30 18:04:53 UTC

OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary