Bug 1629574

Summary: Deployment aborted when installing NAS confiuration on supermicro machines using gluster-colonizer
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Bala Konda Reddy M <bmekala>
Component: gluster-colonizerAssignee: Ramakrishna Reddy Yekulla <rreddy>
Status: CLOSED NOTABUG QA Contact: Rahul Hinduja <rhinduja>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: apaladug, dblack, nchilaka, rhs-bugs, sankarshan, ssaha
Target Milestone: ---Keywords: Reopened, ZStream
Target Release: ---   
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: 2018-10-08 17:21:26 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
Ansible error
none
error none

Description Bala Konda Reddy M 2018-09-17 06:35:09 UTC 
Created attachment 1483893 [details]
Ansible error

Description of problem:
Configured 4 machines with RHGS 3.4.0 booted from PXE(172.18.178.30) with RAID 6. Ran the gluster-colonizer with nas flavour. The playbook failed with error

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

How reproducible:
2/2

Steps to Reproduce:
1. Configured 4 machines with 3.4 from PXE
2. Configured RAID 6 on these 4 machines
3. Ran the gluster-colonizer file with nas.yml
 ]# gluster-colonizer.py -f g1-oemid-smci-nas.yml

Actual results:
Deployment error
Attaching the screenshot for the exact errors

Expected results:
Installation should succeed

Additional info:
IPMI:172.18.178.49(colonizer logs available here)
Comment 2 Dustin Black 2018-09-18 17:03:30 UTC 
This problem is in the OEMID verify file for SMCI, not in the colonizer code. The ansible assert statement that we use to validate the disk count has changed behavior between ansible releases, now reporting devicemapper files. We need to implement a filter in the assert statement to address this.
Comment 3 Dustin Black 2018-09-19 14:36:22 UTC 
This problem was being caused by a rouge USB flash drive plugged into the lab system. Closing BZ.

I wanted to add a note here, too. Any time you have errors, please _always_ include the actual ASCII text of the error in the BZ body somewhere. Showing the errors only in image format means that they will never be indexed searchable in the future to match against and proactively mitigate problems.

-Dustin
Comment 4 Nag Pavan Chilakam 2018-09-21 12:26:59 UTC 
Created attachment 1485486 [details]
error