Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
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"
Status: NEW
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.10.1
Hardware: x86_64
OS: Linux
Target Milestone: GA
: 5.10.z
Assignee: Gregg Tanzillo
QA Contact: Jaroslav Henner
Red Hat CloudForms Documentation
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-27 10:10 UTC by Jaroslav Henner
Modified: 2019-04-07 13:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:

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):

How reproducible:

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.

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