With branch 20221012 as well as 20221014 I get with Fedora Server on BIOS boot Hardware several AVC events like type=AVC msg=audit(1665848517.93:288): avc: denied { sys_admin } for pid=1635 comm="systemd-gpt-aut" capability=21 scontext=system_u:system_r:systemd_gpt_generator_t:s0 tcontext=system_u:system_r:systemd_gpt_generator_t:s0 tclass=capability permissive=0 I can’t find any impairments from it so far. I couldn’t find anything about it besides an old bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1499479 Does anyone have information on whether this can be safely ignored? Some Details: Deploying the ServerKVM immediately after completing the first boot configuration I get 2 times the message systemd-gpt-auto-generator[1169]: Failed to dissect: Permission denied The system proceeds with any problem and finally shows the login prompt. Accordingly I find in audit.log: type=AVC msg=audit(1665836956.540:288): avc: denied { sys_admin } for pid=1249 comm="systemd-gpt-aut" capability=21 scontext=system_u:system_r:systemd_gpt_generator_t:s0 tcontext=system_u:system_r:systemd_gpt_generator_t:s0 tclass=capability permissive=0 The same happens with a standard installation of Fedora Server on hardware. The system boots to login without issues. But as soon as I perform a file operation, e.g. creating log. volume and a filesystem I get the same AVC event. type=AVC msg=audit(1665848517.93:288): avc: denied { sys_admin } for pid=1635 comm="systemd-gpt-aut" capability=21 scontext=system_u:system_r:systemd_gpt_generator_t:s0 tcontext=system_u:system_r:systemd_gpt_generator_t:s0 tclass=capability permissive=0 _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue