https://bugzilla.suse.com/show_bug.cgi?id=1217309 https://bugzilla.suse.com/show_bug.cgi?id=1217309#c5 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #5 from Guillaume GARDET <guillaume.gardet@arm.com> --- (In reply to Matthias Brugger from comment #4)
Created attachment 870894 [details] reboot log
I can now see that the system rebooted, maybe it even rebooted with SELinux enabled, I would need to check. The problem is, that it does not get wifi connection and therefor the clock + date is wrong.
It rebooted with SELinux enabled and journal still shows error: ************************************************** Aug 16 12:00:52 printi setroubleshoot[853]: SELinux is preventing /usr/sbin/rebootmgrd from open access on the file /proc/cpuinfo. For complete SELinux messages run: sealert -l e22cee2c-725a-4bd3-b092-65a27cb7c205 Aug 16 12:00:52 printi setroubleshoot[853]: SELinux is preventing /usr/sbin/rebootmgrd from open access on the file /proc/cpuinfo. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that rebootmgrd should be allowed open access on the cpuinfo file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'rebootmgrd' --raw | audit2allow -M my-rebootmgrd # semodule -X 300 -i my-rebootmgrd.pp ************************************************** So, please open a bug report upstream for this one.
I attach the journal for the boot (-b -0) as well as what gets written to the journal after running
printi:~ # systemctl restart NetworkManager
You can see after reboot the system is not able to start NetworkManager
Aug 16 12:01:12 printi systemd[1]: Failed to start Network Manager Wait Online.
After starting it from hand I have my expected access to the network.
There are lots of MAC addresses settings on boot, which is weird. Maybe ask NetworkManager folks? -- You are receiving this mail because: You are on the CC list for the bug.