Bug 1629574 - Deployment aborted when installing NAS confiuration on supermicro machines using gluster-colonizer
Summary: Deployment aborted when installing NAS confiuration on supermicro machines us...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-colonizer
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ramakrishna Reddy Yekulla
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-17 06:35 UTC by Bala Konda Reddy M
Modified: 2018-10-08 17:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-08 17:21:26 UTC
Embargoed:


Attachments (Terms of Use)
Ansible error (330.84 KB, image/jpeg)
2018-09-17 06:35 UTC, Bala Konda Reddy M
no flags Details
error (515.98 KB, image/jpeg)
2018-09-21 12:26 UTC, Nag Pavan Chilakam
no flags Details

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


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