Bug 1969487 - [FJ OCP4.8 Bug]: Avoid always do delete_configuration clean step
Summary: [FJ OCP4.8 Bug]: Avoid always do delete_configuration clean step
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.8
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 4.8.0
Assignee: Jacob Anders
QA Contact: Raviv Bar-Tal
Depends On:
TreeView+ depends on / blocked
Reported: 2021-06-08 14:07 UTC by Hiroyuki Yasuhara (Fujitsu)
Modified: 2021-07-27 23:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 23:12:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github metal3-io baremetal-operator pull 908 0 None open Avoid always do delete_configuration clean step 2021-06-09 14:35:16 UTC
Github openshift baremetal-operator pull 152 0 None closed Bug 1969487: Disable raid feature for iRMC server 2021-06-10 20:51:51 UTC
Github openshift baremetal-operator pull 153 0 None closed Bug 1969487: Disable RAID for all drivers 2021-06-10 20:51:51 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:12:17 UTC

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:


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:


Hardware configuration:

  Model: RX2540 M4

Target Release:


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.


Note You need to log in before you can comment on or make changes to this bug.