Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1524845

Summary: wodim --devices and other commands fail because of wrong kernel release check in libusal
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: cdrkitAssignee: Jakub Martisko <jamartis>
Status: CLOSED ERRATA QA Contact: Maryna Nalbandian <mnalband>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: fkrska, fsumsal
Target Milestone: rcKeywords: EasyFix, Patch, Reproducer
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cdrkit-1.1.11-24.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 09:49:19 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:
Bug Depends On:    
Bug Blocks: 1549617, 1549689, 1551061    

Description Renaud Métrich 2017-12-12 08:56:40 UTC
Description of problem:

On RHEL7, trying to scan devices using "wodim --devices" or "wodim -scanbus" fails with following error:

wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.

Using strace, we can see that /dev/sg* devices are not scanned.
This is due to a broken test against kernel 2.6 done in libusal, causing kernel "3.10" to be recognized as a "2.x" kernel (x >= 6).


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

wodim-1.1.11-23.el7_4


How reproducible:

Always


Steps to Reproduce:
1. run wodim --devices

Actual results:

wodim: No such file or directory. 
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
For possible transport specifiers try 'wodim dev=help'.
For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from
the wodim documentation.


Expected results:

wodim: Overview of accessible drives (2 found) :
-------------------------------------------------------------------------
 0  dev='/dev/sg0'	rwrw-- : 'QEMU' 'QEMU DVD-ROM'
 1  dev='/dev/sg1'	rwrw-- : 'QEMU' 'QEMU CD-ROM'
-------------------------------------------------------------------------

Comment 11 errata-xmlrpc 2018-10-30 09:49:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3109