| Summary: | cryptsetup should have dependency for device-mapper-libs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Matthew Mosesohn <mmosesoh> |
| Component: | cryptsetup-luks | Assignee: | Milan Broz <mbroz> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | agk, atodorov, mbroz, msanders, pholica, prajnoha, prockai, pvrabec, syeghiay, zkabelac |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | 6.1 | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | cryptsetup-luks-1.2.0-3.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-19 13:30:00 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 609355 | ||
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. Python-cryptsetup doesn't use anything from libdevmapper. But cryptsetup itself probably does, so I'm reassigning to the proper component. 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.) Fixed in cryptsetup-luks-1.2.0-3.el6 # 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.
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 |
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