Bug 1337319
Summary: | rhsmcertd problem connecting to port 9090 due to selinux | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Johan Bergström <johan.bergstrom> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | dwalsh, lvrabec, mgrepl, mmalik, plautrba, pvrabec, ssekidde |
Target Milestone: | beta | ||
Target Release: | 7.3 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.13.1-81.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 02:29:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Johan Bergström
2016-05-18 19:46:40 UTC
We don't maintain SELinux for subscription-manager component ourselves. This is on our SELinux team. Triage notes: When RHEL subscribe to Satellite 6, rhsmcertd component starts communication over HTTPS on port 9090 with Satellite. Please introduce a boolean and if possible, enable it by default so Satellite 6 users don't need to turn it on for each individual system. Applies for all supported RHELs: 5, 6, 7 (where rhsmcertd is available). Thanks. I realized that I was missing the selinux-policy-devel rpm & there is already a module named rhsmcertd, that probably caused the problem with loading the custom module. # semodule -l | grep rhsm rhsmcertd-jb 1.0 rhsmcertd 1.1.1 Re-created it with the name rhsmcertd-jb and it now works fine to load, so workaround is implemented. Lowering prio. And, the product is RHEL7.2, not 6.9. I don't have permission to change it. 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-2016-2283.html |