Bug 692512 - cryptsetup should have dependency for device-mapper-libs
Summary: cryptsetup should have dependency for device-mapper-libs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cryptsetup-luks
Version: 6.1
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: 6.1
Assignee: Milan Broz
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 609355
TreeView+ depends on / blocked
 
Reported: 2011-03-31 13:05 UTC by Matthew Mosesohn
Modified: 2013-03-01 04:10 UTC (History)
10 users (show)

Fixed In Version: cryptsetup-luks-1.2.0-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:30:00 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0597 0 normal SHIPPED_LIVE cryptsetup-luks bug fix and enhancement update 2011-05-18 17:56:35 UTC

Description Matthew Mosesohn 2011-03-31 13:05:05 UTC
Description of problem:
If you upgrade python-cryptsetup and other cryptsetup rpms, you'll run into an error trying to use python-cryptsetup as follows:

# python
Python 2.6.5 (r265:79063, Jan 21 2011, 12:09:23) 
[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import cryptsetup
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: /lib64/libcryptsetup.so.1: symbol dm_task_secure_data, version Base not defined in file libdevmapper.so.1.02 with link time referenc

Version-Release number of selected component (if applicable):
python-cryptsetup-0.0.11-1.el6.x86_64
device-mapper-1.02.53-8.el6_0.4.x86_64 (outdated rpm)

How reproducible:
always

Steps to Reproduce:
1. Install a RHEL 6.0 system with python-cryptsetup
2. Enable RHEL 6.1 beta repository or access from DVD
3. Update python-cryptsetup, cryptsetup-luks, and cryptsetup-luks-libs
4. run python in command line, and type "import cryptsetup"

  
Actual results:
The error provided in description

Expected results:
The library should work

Additional info:
There should be a version-specific dependency in the python-cryptsetup rpm

Comment 2 RHEL Program Management 2011-03-31 13:37:56 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Martin Sivák 2011-03-31 13:46:54 UTC
Python-cryptsetup doesn't use anything from libdevmapper. But cryptsetup itself probably does, so I'm reassigning to the proper component.

Comment 4 Milan Broz 2011-03-31 14:11:28 UTC
That change is because of FIPS checks and there should be explicit Require from cryptsetup-libs on new device-mapper libs.

What's the version of installed device-mapper-libs?

If you install cryptsetup-luks-devel package, will it update device-mapper libs?
(Seems that req. is wrongly just for devel package.)

Comment 7 Milan Broz 2011-04-04 20:20:02 UTC
Fixed in cryptsetup-luks-1.2.0-3.el6

Comment 9 Alexander Todorov 2011-04-18 13:25:37 UTC
# rpm -q cryptsetup-luks-libs 
cryptsetup-luks-libs-1.2.0-3.el6.x86_64

# rpm -qR cryptsetup-luks-libs | grep mapper
device-mapper-libs >= 1.02.61
libdevmapper.so.1.02()(64bit)  
libdevmapper.so.1.02(Base)(64bit)  

# python 
Python 2.6.6 (r266:84292, Apr 11 2011, 15:50:32) 
[GCC 4.4.4 20100726 (Red Hat 4.4.4-13)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import cryptsetup
>>> 


Moving to VERIFIED.

Comment 10 errata-xmlrpc 2011-05-19 13:30:00 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0597.html


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