Bug 1045329 - subscription-manager can't work in fips mode.
Summary: subscription-manager can't work in fips mode.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: 1113520 rhsm-rhel72 1205796
TreeView+ depends on / blocked
 
Reported: 2013-12-20 07:42 UTC by xingge
Modified: 2016-09-20 02:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 11:48:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2122 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2015-11-19 10:31:14 UTC

Description xingge 2013-12-20 07:42:19 UTC 
Description of problem:
subscription-manager can't work in fips mode.

Version-Release number of selected component (if applicable):
subscription-manager-1.10.8-1.el7
subscription-manager-gui-1.10.8-1.el7
subscription-manager-firstboot-1.10.8-1.el7
python-rhsm-1.10.8-1.el7

How reproducible:


Steps to Reproduce:
1.Install dracut-fips with cmd "yum install dracut-fips -y"
2.Open /boot/grub2/grub.cfg add "fips=1" in the line "linux16 /vmlinuz ***"
3.Reboot the system
4.run subscription-manager modules like "subscription-manager list --consumed"

Actual results:
After run some subscription-manager cmd the cmd will keep running without any results untill I close the CLI window.

Expected results:
The cmd should give the results in a reasonable time.

Additional info:
Comment 3 William Poteat 2015-05-12 18:50:02 UTC 
Old bug. Still a problem?
Comment 4 xingge 2015-06-10 02:27:33 UTC 
not a problem now
Comment 6 errata-xmlrpc 2015-11-19 11:48:02 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://rhn.redhat.com/errata/RHBA-2015-2122.html
Note You need to log in before you can comment on or make changes to this bug.