Hide Forgot
Description of problem: # semanage fcontext -l | grep /etc/Pegasus /etc/Pegasus(/.*)? all files system_u:object_r:pegasus_conf_t:s0 /etc/Pegasus/pegasus_current\.conf all files system_u:object_r:pegasus_data_t:s0 # But the service does not create / use any file called pegasus_current.conf. The service creates / uses a file called cimserver_current.conf. Version-Release number of selected component (if applicable): selinux-policy-3.7.19-281.el6.noarch selinux-policy-doc-3.7.19-281.el6.noarch selinux-policy-minimum-3.7.19-281.el6.noarch selinux-policy-mls-3.7.19-281.el6.noarch selinux-policy-targeted-3.7.19-281.el6.noarch tog-pegasus-2.12.0-3.el6_4.x86_64 tog-pegasus-libs-2.12.0-3.el6_4.x86_64 How reproducible: always Steps to Reproduce: # service tog-pegasus start Starting up CIM server: [ OK ] # service tog-pegasus status CIM server (11285) is running # service tog-pegasus stop Shutting down CIM server: [ OK ] # restorecon -Rv /etc/Pegasus/ restorecon reset /etc/Pegasus/cimserver_current.conf context unconfined_u:object_r:pegasus_data_t:s0->unconfined_u:object_r:pegasus_conf_t:s0 # restorecon -Rv /etc/Pegasus/ # Actual results: * the file context pattern contains an invalid filename Expected results: * the file context pattern contains a correct filename
Milos, I see it also on RHEL-7. Can you confirm it?
Yes, that was the reason for filing BZ#1278777.
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-0763.html