Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 941730[details]
audit.log
Description of problem:
This is a problem that was seen and fixed in Fedora 20 (BZ 1110040) and is now spotted in RHEL7.
Version-Release number of selected component (if applicable):
openstack-selinux-0.5.15-1.el7ost.noarch
selinux-policy-3.12.1-153.el7_0.10.noarch
selinux-policy-targeted-3.12.1-153.el7_0.10.noarch
How reproducible:
always
Steps to Reproduce:
1. Using instack-undercloud, deploy overcloud using source and run instack-test-overcloud.
Actual results:
neutron-ns-meta denied connectto on unix_stream_socket
Expected results:
no denial
Additional info:
audit.log.1:type=AVC msg=audit(1411756457.879:6476): avc: denied { connectto } for pid=11611 comm="neutron-ns-meta" path="/run/neutron/metadata_proxy" scontext=system_u:system_r:neutron_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=unix_stream_socket
[root@overcloud-controller0-hkj4j63jzxat ~]# ps -efZ | grep neutron-ns
system_u:system_r:neutron_t:s0 root 11611 1 0 14:31 ? 00:00:00 /opt/stack/venvs/openstack/bin/python /bin/neutron-ns-metadata-proxy --pid_file=/var/run/neutron/external/pids/52e157df-9ccb-4690-9994-dc1b1c3926be/pid --metadata_proxy_socket=/var/run/neutron/metadata_proxy --router_id=52e157df-9ccb-4690-9994-dc1b1c3926be --state_path=/var/run/neutron --metadata_port=9697
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 19634 19265 0 18:37 pts/0 00:00:00 grep --color=auto neutron-ns
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-2015-0458.html