xsuchy / fedora-upgrade

Upgrade Fedora to next version using DNF upgrade without the need to reboot during the upgrade.
GNU General Public License v2.0
43 stars 16 forks source link

[F17->F18] Fix issues with polkit aka Authorization Manager after reboot #3

Closed lionaneesh closed 11 years ago

lionaneesh commented 11 years ago

The authorization manager fails to start after the system update. The problem can be fixed by re-installing the polkit and systemd before reboot.

dgoodwin commented 11 years ago

Didn't test the patch per-se just tried to run the command after my fedora-upgrade completed but before reboot and got this:

(root@redhat ~) $ yum reinstall polkit systemd error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch error: cannot open Packages index using db5 - (-30969) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main:

Error: rpmdb open failed

From this thread:

http://lists.fedoraproject.org/pipermail/devel/2012-June/169494.html

I just ran: rm -rf /var/lib/rpm/__db.00*

And the reinstall now worked. May want to incorporate this into the patch but I'm not sure, I think it's safe, I've seen it used before with rpmdb issues.

dgoodwin commented 11 years ago

Able to login fine after reboot.

lionaneesh commented 11 years ago

Able to login fine after reboot.

You mean without re-installing? That can be the case for your system but It doesn't on my Intel core i3 with Fedora 17 x86_64, the yum update somehow causes the Authorization Manager to mess up. The service won't start.

dgoodwin commented 11 years ago

No with reinstalling, I.e. your fix worked. (Or my system wasn't going to break in that manner anyhow)

xsuchy commented 11 years ago

I believe that this problem happens in past due bug https://bugzilla.redhat.com/show_bug.cgi?id=844167 Can you confirm that you have to reinstall those packages even with selinux-policy-3.10.0-149.fc17 ?

xsuchy commented 11 years ago

@dgoodwin This is exactly the reason why I have rpm --rebuilddb just after yum --releasever=18 --disableplugin=presto distro-sync

xsuchy commented 11 years ago

@lionaneesh can you please test this fix?