Bug 1693189 - /dev/sr0 among the block devices in menu "Choose the database disk"
Summary: /dev/sr0 among the block devices in menu "Choose the database disk"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.10.1
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: GA
: 5.12.0
Assignee: drew uhlmann
QA Contact: Jaroslav Henner
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks: 1784561
TreeView+ depends on / blocked
 
Reported: 2019-03-27 10:10 UTC by Jaroslav Henner
Modified: 2020-05-19 17:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1784561 (view as bug list)
Environment:
Last Closed: 2020-03-25 18:03:19 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Henner 2019-03-27 10:10:17 UTC
Description of problem:
When creating the DB using the appliance console, the user is given the option to create it on /dev/sr0 which is a SCSI CDROM. Creating the DB on it will not ever succeed.

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

How reproducible:
always

Steps to Reproduce:
1. Opt the CFME 5.10 from sprout on RHEVM provider
2. Configure database using appliance_console
3. Answer the quiestions until you get to 'Choose the database disk: |1| '

Actual results:
    # On 5.10, rhevm provider:
    #
    #    database disk
    #
    #    1) /dev/sr0: 0 MB
    #    2) /dev/vdb: 4768 MB
    #    3) Don't partition the disk

Expected results:
    # On 5.10, rhevm provider:
    #
    #    database disk
    #
    #    1) /dev/vdb: 4768 MB
    #    2) Don't partition the disk

Additional info:

Comment 2 Reartes Guillermo 2019-04-07 13:23:38 UTC
On VMWARE and CF 4.7, i also saw /dev/fd0 as an option.

Comment 3 drew uhlmann 2019-10-01 13:40:37 UTC
LJ and I were looking at this and determined that the issue isn't with the appliance OVAs. I think https://github.com/ManageIQ/linux_admin/commit/eaff9fccfb16dd111a4bbf45d561a1afd09ad9c4 introduced this issue since previously we were filtering out both /dev/fd0 and /dev/sr0 (it was previously `Dir.glob(['/dev/[vhs]d[a-z]', '/dev/xvd[a-z]']).collect`). The conclusion that LJ and I drew is that we could fix this by adding filtering on the linux admin side, since the filtering options available to us via lsblk seem rather limited. Specifically, the approach is to remove all block devices from the list with a size zero.

Comment 5 drew uhlmann 2019-11-11 11:38:29 UTC
Please disregard comment 4, in its stead, see https://github.com/ManageIQ/linux_admin/pull/214


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