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.

Description of problem:
The watchdog daemon runs with incorrect selinux context.

Version-Release number of selected component (if applicable):
selinux-policy-3.7.19-154.el6.noarch
selinux-policy-targeted-3.7.19-154.el6.noarch
watchdog-5.5-10.el6.x86_64

How reproducible:
always

Steps to Reproduce:
# service watchdog status
watchdog (pid  9121) is running...
# ps -elZ | grep 9121
unconfined_u:system_r:initrc_t:s0 5 S   0  9121     1  0  58   - -  1032 hrtime ?        00:00:00 watchdog

Actual results:
it runs with initrc_t

Expected results:
it should run with its own selinux label

Additional info:

OK ...  I have no clue how to fix this, so I'm
going to reassign it to selinux-policy.

I see we have policy files but the policy is not activated for a reason.

Patrik,
does it cause any issue?

Do you see AVC msgs?

(In reply to comment #3)
> I see we have policy files but the policy is not activated for a reason.
> 
> Patrik,
> does it cause any issue?
> 
> Do you see AVC msgs?

Actually not, there are no AVCs, but I do not do any testing with watchdog, just started it a saw the initrc_t label.
Isn't that an error itself?

Yes, it is.

But it is also pretty risky to add a new policy in this phase without testing in Fedora at least.

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-2013-1598.html