On 25 November 2016 at 16:08, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote:
> With selinux set to enforcing, my system-upgrade to 25 failed to start,
> resulting in a reboot loop. I fished the following out of journalctl:
>
> Nov 25 09:51:55 thinkpenguin.email-scan.com audit[1]: AVC avc: denied {
> open } for pid=1 comm="systemd"
> path="/var/lib/dnf/system-upgrade/.dnf-system-upgrade" dev="dm-1"
> ino=1181602 scontext=system_u:system_r:init_t:s0
>
> I had to drop to an emergency shell, and set selinux to permissive, in order
> for the upgrade to do its thing.
>
> Wondering if all upgrades with selinux enabled are broken, or just something
> with this particular laptop. This doesn't look like a system-specific
> failure to me, but if all upgrades with enforcing selinux blow up like this,
> I would've expected a lot of noise in here, by now… More details in bug
> 1398696.
>
>
For what it's worth my systems are always Enforcing ... two laptops
upgraded (one in beta and one in RC) with no problem and a headless
server at release with no problem
There must be something off with your setup somehow
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
