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

Bug 1879865

Summary: OCS 4.6 Installation failed to detect nvme/ssd disk in the nodes for BM
Product: OpenShift Container Platform Reporter: Pratik Surve <prsurve>
Component: Console Storage PluginAssignee: Ankush Behl <anbehl>
Status: CLOSED ERRATA QA Contact: Pratik Surve <prsurve>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, nberry, nthomas
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 16:41: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:
Attachments:
Description Flags
Screenshot form install wizard none

Description Pratik Surve 2020-09-17 08:51:20 UTC 
Description of problem:
OCS 4.6 Installation wizard failed to detect nvme/ssd disk in the nodes even of there are enough disk present 

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

OCP version:- 4.6.0-0.nightly-2020-09-16-175801
OCS version:- ocs-operator.v4.6.0-88.ci
LSO version:- local-storage-operator.4.6.0-202009082256.p0

How reproducible:
Always when ssd/nvm disk are present on nodes

Steps to Reproduce:
1. Deploy OCP 4.6
2. Deploy 4.6 LSO operator 
3. Deploy OCS 4.6 operator
4. Create storagecluster

Actual results:
attaching screenshot 

Expected results:
Node and it's disk should be detected 

Additional info:

Starting pod/ip-10-0-131-178us-east-2computeinternal-debug ...
To use host binaries, run `chroot /host`
NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme2n1                      259:0    0   2.3T  0 disk 
nvme1n1                      259:1    0   2.3T  0 disk 
nvme0n1                      259:2    0   120G  0 disk 
|-nvme0n1p1                  259:3    0   384M  0 part /boot
|-nvme0n1p2                  259:4    0   127M  0 part /boot/efi
|-nvme0n1p3                  259:5    0     1M  0 part 
`-nvme0n1p4                  259:6    0 119.5G  0 part 
  `-coreos-luks-root-nocrypt 253:0    0 119.5G  0 dm   /sysroot

Removing debug pod ...
Starting pod/ip-10-0-184-227us-east-2computeinternal-debug ...
To use host binaries, run `chroot /host`
NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme2n1                      259:0    0   2.3T  0 disk 
nvme1n1                      259:1    0   2.3T  0 disk 
nvme0n1                      259:2    0   120G  0 disk 
|-nvme0n1p1                  259:3    0   384M  0 part /boot
|-nvme0n1p2                  259:4    0   127M  0 part /boot/efi
|-nvme0n1p3                  259:5    0     1M  0 part 
`-nvme0n1p4                  259:6    0 119.5G  0 part 
  `-coreos-luks-root-nocrypt 253:0    0 119.5G  0 dm   /sysroot

Removing debug pod ...
Starting pod/ip-10-0-210-134us-east-2computeinternal-debug ...
To use host binaries, run `chroot /host`
NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme1n1                      259:0    0   2.3T  0 disk 
nvme2n1                      259:1    0   2.3T  0 disk 
nvme0n1                      259:2    0   120G  0 disk 
|-nvme0n1p1                  259:3    0   384M  0 part /boot
|-nvme0n1p2                  259:4    0   127M  0 part /boot/efi
|-nvme0n1p3                  259:5    0     1M  0 part 
`-nvme0n1p4                  259:6    0 119.5G  0 part 
  `-coreos-luks-root-nocrypt 253:0    0 119.5G  0 dm   /sysroot

Removing debug pod ...
Comment 1 Pratik Surve 2020-09-17 08:52:04 UTC 
Created attachment 1715194 [details]
Screenshot form install wizard
Comment 7 errata-xmlrpc 2020-10-27 16:41:53 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 (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