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.
Bug 2055199 - avc: denied { execute } for comm="nm-dispatcher" name="04-iscsi" on every boot
Summary: avc: denied { execute } for comm="nm-dispatcher" name="04-iscsi" on every...
Keywords:
Status: CLOSED DUPLICATE of bug 1989070
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.6
Assignee: Zdenek Pytela
QA Contact: BaseOS QE Security Team
URL:
Whiteboard: CockpitTest
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-16 13:13 UTC by Martin Pitt
Modified: 2022-08-24 09:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-16 13:33:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112559 0 None None None 2022-02-16 13:24:32 UTC

Description Martin Pitt 2022-02-16 13:13:01 UTC 
Description of problem: Our latest RHEL 8.6 image refresh [1] found a regression in nightly that affects every boot.


Version-Release number of selected component (if applicable):

selinux-policy (3.14.3-89.el8 -> 3.14.3-91.el8)

The image refresh updated a few other pages, see the bottom of [2] for details. But specifically, NetworkManager did *not* update.


How reproducible: Always

Steps to Reproduce:
1. Boot current RHEL 8.6 nightly cloud image


Actual results:

NetworkManager[884]: <info>  [1645016850.5617] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
NetworkManager[884]: <info>  [1645016850.5634] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
NetworkManager[884]: <info>  [1645016850.5638] device (virbr0): Activation: starting connection 'virbr0' (05d6de47-9aa0-4d7f-8015-0a2039c4f0cd)
NetworkManager[884]: <info>  [1645016850.5639] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
NetworkManager[884]: <info>  [1645016850.5641] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
NetworkManager[884]: <info>  [1645016850.5641] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
NetworkManager[884]: <info>  [1645016850.5642] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
nm-dispatcher[922]: req:7 'pre-up' [virbr0]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d/pre-up.d': Error opening directory “/etc/NetworkManager/dispatcher.d/pre-up.d”: Permission denied
NetworkManager[884]: <info>  [1645016850.5670] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
nm-dispatcher[922]: req:8 'up' [virbr0]: find-scripts: Failed to open dispatcher directory '/etc/NetworkManager/dispatcher.d': Error opening directory “/etc/NetworkManager/dispatcher.d”: Permission denied
NetworkManager[884]: <info>  [1645016850.5671] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
nm-dispatcher[922]: req:8 'up' [virbr0], "/usr/lib/NetworkManager/dispatcher.d/04-iscsi": complete: failed to execute script: Failed to execute child process “/usr/lib/NetworkManager/dispatcher.d/04-iscsi” (Permission denied)
NetworkManager[884]: <info>  [1645016850.5673] device (virbr0): Activation: successful, device activated.
kernel: audit: type=1400 audit(1645016850.567:9): avc:  denied  { execute } for  pid=1598 comm="nm-dispatcher" name="04-iscsi" dev="vda3" ino=9978578 scontext=system_u:system_r:NetworkManager_dispatcher_t:s0 tcontext=system_u:object_r:NetworkManager_dispatcher_script_t:s0 tclass=file permissive=0
NetworkManager[884]: <warn>  [1645016850.5737] dispatcher: (8) /usr/lib/NetworkManager/dispatcher.d/04-iscsi failed (exec failed): Failed to execute child process “/usr/lib/NetworkManager/dispatcher.d/04-iscsi” (Permission denied)


Expected results: That shouldn't happen :-)


Additional info:

[1] https://github.com/cockpit-project/bots/pull/2940
[2] https://logs.cockpit-project.org/logs/image-refresh-2940-20220215-022121/log
Comment 1 Zdenek Pytela 2022-02-16 13:33:20 UTC 

*** This bug has been marked as a duplicate of bug 1989070 ***
Note You need to log in before you can comment on or make changes to this bug.