F21 -> F22: SELinux, NetworkManager and Xorg (unresponsive post distro-sync)

[kashyapc at fedoraproject.org]

On Sat, Mar 14, 2015 at 11:04:44PM +0100, kashyapc at fedoraproject.org wrote:
> The below is after I updated from F21 to F22 on a Lenovo X220 baremetal.
> 
> No, first, I must mention: the machine was running Fedora 20, so I did a
> `fedup --network 21 --product=workstation` followed by duplicate
> cleanups, all of which went smoothly.
> 
> Then, I moved to F22. Events in order:
> 
>   (1) Upgrade:
> 
>         $ dnf --refresh --releasever=f21 distro-sync 

Typo, I obviously meant: s/f21/22

This was a bad thing that I did: using `dnf distro-sync` to upgrade from
F21 to F22 instead of `fedup` while we're in the middle of replacing
'yum' with 'dnf'. I should have used either `yum` or should have
`restorecon -R /` before rebooting!

>         $ reboot
> 
>   (2) Boot fails, because it's stuck at:
>   
>         "Failed to load SELinux policy. Freezing". 
>       
>       Reboot and go with 'enforcing=0' on Kernel command line, to get a
>       successful boot. (SELinux policy version:
>       selinux-policy-3.13.1-116.fc22.noarch)

On a system that I reprovisioned due to various other issues, I was
hitting this bug:

    https://bugzilla.redhat.com/show_bug.cgi?id=1204488 --  `dnf update`
    results in "CRITICAL Failed to obtain the transaction lock (logged
    in as: root)."

Wonder if it's legitmate. I briefly popped into #yum on Freenode, and
one of the `dnf` developers said the above bug could likely be an RPM
issue.

But if anyone else can reproduce it or not, remained to be seen.

-- 
/kashyap