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:
I can see some avc denials and my beaker jobs are failing because of it.. I use dogtail to bring Xorg up and then I create profiles via dogtail and nm-connection-editor.. no errors while executed by hand.
can this be initrc_t bug? don't know exactly how beaker operates it's scripts


Version-Release number of selected component (if applicable):
beaker-6.1
selinux-policy-3.7.19-54.el6.noarch

https://beaker.engineering.redhat.com/jobs/43864
^^^ this job is affected

How reproducible:
100%

Steps to Reproduce:
1.execute dogtail job in beaker

  
Actual results:
avc errors and thus job failure

Expected results:
no errors, no failures 

Additional info:

You probably need to run this using runcon to get it running as unconfined_t.

(In reply to comment #2)
> You probably need to run this using runcon to get it running as unconfined_t.

I wonder if we'll want to file an RFE on Beaker - seems a lot of tests would be more appropriately run as unconfied_t rather than inirc_t

Tests of user apps should be done as unconfined_t, tests of system apps/daemons should be done as initrc_t.

newest beah harness will run tests as unconfined_t by default.  This will be in the next release.

For record changing to duplicate.

*** This bug has been marked as a duplicate of bug 669665 ***