Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1964203

Summary: e2e-metal-ipi, e2e-metal-ipi-ovn-dualstack and e2e-metal-ipi-ovn-ipv6 are failing due to "Unknown provider baremetal"
Product: OpenShift Container Platform Reporter: Aravindh Puthiyaparambil <aravindh>
Component: Bare Metal Hardware ProvisioningAssignee: Arda Guclu <aguclu>
Bare Metal Hardware Provisioning sub component: baremetal-operator QA Contact: Amit Ugol <augol>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: high CC: aguclu, rbartal, rpittau, wking
Version: 4.7Keywords: Triaged
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 23:10:05 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:

Description Aravindh Puthiyaparambil 2021-05-25 01:37:58 UTC 
Description of problem:
e2e-metal-ipi [0], e2e-metal-ipi-ovn-dualstack [1] and e2e-metal-ipi-ovn-ipv6 [2] are failing consistently with "E0524 16:11:58.410663 75520 test_context.go:485] Unknown provider "baremetal". The following providers are known: aws azure gce gke ibmcloud kubemark kubevirt local openstack ovirt skeleton vsphere"

[0] https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/763/pull-ci-openshift-kubernetes-release-4.7-e2e-metal-ipi/1396834420287082496
[1] https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/763/pull-ci-openshift-kubernetes-release-4.7-e2e-metal-ipi-ovn-dualstack/1396834420370968576
[2] https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/763/pull-ci-openshift-kubernetes-release-4.7-e2e-metal-ipi-ovn-ipv6/1396834420563906560


How reproducible: always

Additional info:

According to @stbenjam we either need to backport openshift/origin#25994 [3] and openshift/origin#26007 [4] to 4.7 (and likely 4.6, too) or don't specify the provider on < 4.8 [5]

Slack thread [6]

[3] https://github.com/openshift/origin/pull/25994
[4] https://github.com/openshift/origin/pull/26007
[5] https://github.com/openshift/release/blob/master/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-commands.sh#L54-L59
[6] https://coreos.slack.com/archives/CEKNRGF25/p1621894618037900
Comment 4 errata-xmlrpc 2021-07-27 23:10:05 UTC 
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438