Bug 1386375 - rhscon-agent unable to detect OSD devices that have been encrypted
Summary: rhscon-agent unable to detect OSD devices that have been encrypted
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: agent
Version: 2
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: 3
Assignee: Shubhendu Tripathi
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-18 19:32 UTC by Kyle Squizzato
Modified: 2020-06-11 13:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:41:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Kyle Squizzato 2016-10-18 19:32:13 UTC 
Description of problem:
Importing a newly created cluster into RHSC where the OSD devices have been encrypted with dm-crypt results in all OSD hosts not 

Version-Release number of selected component (if applicable):
rhscon-agent-0.0.18-1.el7scon.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a cluster using the CLI
2. During OSD creation, encrypt the disks with dm-crypt 
3. Attempt to import the cluster into RHSC

Actual results:
Imported cluster OSD hosts show no active OSDs

Expected results:
Imported cluster OSD hosts should show OSD count, even if they're encrypted.

Additional info:
Per BZ https://bugzilla.redhat.com/1373736 dm-crypt support is coming to 2.1.  We'll probably want to have the RHSC agent able to identify encrypted OSDs for that release.
Comment 2 Shubhendu Tripathi 2018-11-19 05:41:57 UTC 
This product is EOL now
Note You need to log in before you can comment on or make changes to this bug.