On Mon, 2019-02-11 at 15:21 -0500, pmkellly@xxxxxxxxxxxx wrote: > The 0211 ISO was downloaded, check sum checked, burned to DVD, and used > to boot a bare metal PC (Lenovo M58p with E8400 processor). all of that > ran good with no problem. The media check passed and Anaconda started > with no problems. During install disk selection the delete all and > recover options were selected. The install completed with no problems. I > ran all of the Basic test cases and they passed. > > Then I started testing in my deployment mode. I ran a script that > removed the software not used here and installed the software that is. > One of the items I installed was the SELinux alert browser. I mention > this because after the system rebooted I started getting a continuing > stream of SELinux Alerts. I literally got hundreds of alerts though the > browser only shows 16 with many occurrences listed for each one and they > are all the same: > > The source process: systemd-journald > Attempted this access: signull > On this proccess: (blank) > > The system is still functional if you can put up with all the alerts. > > I have attached some files which I hope will provide more details. I > would report this as a bug, but It's not clear to me that systemd is at > fault, but then I'm still in learning mode. Thanks, this is already known: https://bugzilla.redhat.com/show_bug.cgi?id=1673847 A new selinux-policy should fix it soon. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
