Bug 717654
Summary: | subscription-manager does not have it's own policy | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Miroslav Grepl <mgrepl> |
Component: | subscription-manager | Assignee: | Bryan Kearney <bkearney> |
Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | CC: | awood, bkearney, dwalsh, jkortus, jmolet, jsefler, mmalik, syeghiay |
Target Milestone: | rc | ||
Target Release: | 6.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 694879 | Environment: | |
Last Closed: | 2011-12-06 17:19:36 UTC | Type: | --- |
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: | 694879 | ||
Bug Blocks: | 682238, 748554 |
Comment 1
Miroslav Grepl
2011-06-29 13:49:07 UTC
Well not sure why this fix is not going to RHEL6.2. This relates with policy changes. Committed be21aa786f3df02dda1257dd0b5ef575f119ad9d running rhel6.2 snapshot 3, which uses rhsm versions: subscription-manager-0.96.16-1.el6.x86_64 subscription-manager-firstboot-0.96.16-1.el6.x86_64 subscription-manager-gnome-0.96.16-1.el6.x86_64 rhsmcertd appears to be confined at startup: ps auxfwwwZ | grep /usr/bin/rhsmcertd | grep -v grep system_u:system_r:rhsmcertd_t:s0 root 1989 0.0 0.0 4112 404 ? Ss Oct24 0:00 /usr/bin/rhsmcertd 240 1440 system_u:system_r:rhsmcertd_t:s0 root 1991 0.0 0.0 4112 404 ? S Oct24 0:00 \_ /usr/bin/rhsmcertd 240 1440 rhsmcertd has its own binary context: [root@jmolet-rhel62s3 ~]# ls -laZ /usr/bin/rhsmcertd -rwxr-xr-x. root root system_u:object_r:rhsmcertd_exec_t:s0 /usr/bin/rhsmcertd 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. http://rhn.redhat.com/errata/RHBA-2011-1695.html |