Bug 1969487

Summary:	[FJ OCP4.8 Bug]: Avoid always do delete_configuration clean step
Product:	OpenShift Container Platform	Reporter:	Hiroyuki Yasuhara (Fujitsu) <hyasuhar>
Component:	Bare Metal Hardware Provisioning	Assignee:	Jacob Anders <janders>
Bare Metal Hardware Provisioning sub component:	baremetal-operator	QA Contact:	Raviv Bar-Tal <rbartal>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	hshiina, hyasuhar, janders, jniu, rbartal, rpittau, tsedovic, zbitter
Version:	4.8	Keywords:	OtherQA, Triaged
Target Milestone:	---
Target Release:	4.8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 23:12:04 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 Hiroyuki Yasuhara (Fujitsu) 2021-06-08 14:07:10 UTC

Description of Problem:

  When I test on a Fujitsu iRMC server without a RAID controller, this will cause an error.
  In case of Fujitsu iRMC server, OCP always tries to clean current RAID setting during deployment.
  In this case, an error will occur if we try to clean against non-RAID server.
  And then, OCP deployment fails.

Version-Release number of selected component:

  Red Hat OpenShift Container Platform Version Number:4.8
  Release Number:4.8.0-0.nightly-2021-06-06-164529

Drivers or hardware or architecture dependency:

  Fujitsu iRMC

How reproducible:

  Always

Step to Reproduce:

  $ openshift-install --dir ~/clusterconfigs create manifests
  $ cp ~/ipi/99_router-replicas.yaml ~/clusterconfigs/openshift/
  $ openshift-install --dir ~/clusterconfigs --log-level debug create cluster

Actual Results:

  In case of iRMC, OCP always does delete_configuration clean step.
  This means that OCP cleans current RAID setting even if we don't set RAID via BareMetalHost.
  This cause unintentional loss of RAID settings.

Expected Results:

  Not clean current RAID setting if we don't set RAID via BareMetalHost.
  This means that we don't change current RAID setting in the servers and we use that.

Summary of actions taken to resolve issue:

  Fujitsu sent PR in metal3-io ( https://github.com/metal3-io/baremetal-operator/pull/908 ).

Location of diagnostic data:

  None

Hardware configuration:

  Model: RX2540 M4

Target Release:

  OCP4.8

Comment 2 Raviv Bar-Tal 2021-06-15 08:35:44 UTC

Bug move to verified as other qa so it will not block the code from been publish in the release.

Comment 5 errata-xmlrpc 2021-07-27 23:12:04 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