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 713456 - Move "Running in FIPS mode." to more verbose level to not break scripts
Summary: Move "Running in FIPS mode." to more verbose level to not break scripts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cryptsetup-luks
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Milan Broz
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 713410
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-15 13:13 UTC by RHEL Program Management
Modified: 2013-03-01 04:10 UTC (History)
8 users (show)

Fixed In Version: cryptsetup-luks-1.2.0-3.el6_1.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-20 07:09:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0884 0 normal SHIPPED_LIVE cryptsetup-luks bug fix update 2011-06-20 07:09:22 UTC

Description RHEL Program Management 2011-06-15 13:13:28 UTC
This bug has been copied from bug #713410 and has been proposed
to be backported to 6.1 z-stream (EUS).

Comment 4 Milan Broz 2011-06-15 13:27:44 UTC
Fixed in cryptsetup-luks-1.2.0-3.el6_1.2.

Comment 6 Alexander Todorov 2011-06-15 15:50:11 UTC
# cat /proc/cmdline 
ro root=/dev/mapper/vg_dellpesc142001-lv_root boot=UUID=f2e92c68-b390-44a0-8a44-c1d45c36b677 rd_LVM_LV=vg_dellpesc142001/lv_root rd_LVM_LV=vg_dellpesc142001/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us fips=1 console=ttyS0,115200 

# rpm -q cryptsetup-luks
cryptsetup-luks-1.2.0-3.el6.x86_64

# cryptsetup isLuks /dev/sda
Running in FIPS mode.
Device /dev/sda is not a valid LUKS device.

After update: 

# rpm -q cryptsetup-luks
cryptsetup-luks-1.2.0-3.el6_1.2.x86_64

# cryptsetup isLuks /dev/sda
Device /dev/sda is not a valid LUKS device.

# cryptsetup -v isLuks /dev/sda
Running in FIPS mode.
Device /dev/sda is not a valid LUKS device.
Command failed with code 22: Device /dev/sda is not a valid LUKS device.


"Running in FIPS mode." message is printed only in verbose mode.

Comment 7 errata-xmlrpc 2011-06-20 07:09:31 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-0884.html


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