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.

Created attachment 1243002 [details]
audit2allow -w -a output

Description of problem:
  Cannot start zabbix-agent with selinux enforcing after updating to 3.0.7-1.el7

Version-Release number of selected component (if applicable):
  3.0.7-1.el7

How reproducible:
  Happened on 3 of my servers right after update

Steps to Reproduce:
1. Update to zabbix-agent 3/0/7-1.el7
2. Run systemctl start zabbix-agent

Actual results:
  Service fails to start

Expected results:
  Service starts

Additional info:
  Reporting because this page told me to: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html


##### sudo audit2allow -a #####

#============= logrotate_t ==============
allow logrotate_t init_t:service reload;

#============= named_t ==============

#!!!! This avc can be allowed using the boolean 'named_write_master_zones'
allow named_t named_zone_t:dir write;

#============= systemd_sysctl_t ==============
allow systemd_sysctl_t user_home_t:file read;

#============= unconfined_t ==============
allow unconfined_t init_t:service enable;
allow unconfined_t zabbix_agent_t:file relabelto;

#============= zabbix_agent_t ==============
allow zabbix_agent_t self:process setrlimit;


#####  #####

#============= zabbix_agent_t ==============
allow zabbix_agent_t self:process setrlimit;

Is already reported in BZ#1393332.

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