Hi all,
I tried to upgrade to F23 with dnf system-upgrade last night. The download part went smoothly. But it failed during the reboot stage. On booting again, I noticed grub has not been updated, that's when I realised the upgrade had failed. In the journal I see something like this:
python3[769]: Starting system upgrade. This will take a while. dnf[769]: Dependencies resolved. dnf[769]: Error: The operation would result in removing the following protected packages: dnf, systemd. systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: dnf-system-upgrade.service: Failed to load environment files: No such file or directory systemd[1]: dnf-system-upgrade.service: Failed to run 'stop-post' task: No such file or directory systemd[1]: dnf-system-upgrade.service: Unit entered failed state. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: dnf-system-upgrade.service: Failed with result 'resources'. systemd[1]: Rebooting as result of failure.
When I tried distro-sync with --allowerasing, I encounter the exact same error. I found a similar unresolved bug report (with incomplete information), but no other results turned up from a quick search. Any thoughts?
Cheers,
From: "Suvayu Ali" fatkasuvayu+linux@gmail.com
Hi all,
I tried to upgrade to F23 with dnf system-upgrade last night. The download part went smoothly. But it failed during the reboot stage. On booting again, I noticed grub has not been updated, that's when I realised the upgrade had failed. In the journal I see something like this:
python3[769]: Starting system upgrade. This will take a while. dnf[769]: Dependencies resolved. dnf[769]: Error: The operation would result in removing the following protected packages: dnf, systemd. systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: dnf-system-upgrade.service: Failed to load environment files: No such file or directory systemd[1]: dnf-system-upgrade.service: Failed to run 'stop-post' task: No such file or directory systemd[1]: dnf-system-upgrade.service: Unit entered failed state. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: dnf-system-upgrade.service: Failed with result 'resources'. systemd[1]: Rebooting as result of failure.
When I tried distro-sync with --allowerasing, I encounter the exact same error. I found a similar unresolved bug report (with incomplete information), but no other results turned up from a quick search. Any thoughts?
The same happened to me too. F21->f22 upgrade went fine but when updating from F22 to F23 I was not able to boot into system upgrade splash screen. Maybe it's related to this [1] bug report.
Honza
Op Wed, 03 Feb 2016 11:08:45 +0100 schreef Honza Šilhan jsilhan@redhat.com:
From: "Suvayu Ali" fatkasuvayu+linux@gmail.com
Hi all,
I tried to upgrade to F23 with dnf system-upgrade last night. The download part went smoothly. But it failed during the reboot stage. On booting again, I noticed grub has not been updated, that's when I realised the upgrade had failed. In the journal I see something like this:
python3[769]: Starting system upgrade. This will take a while. dnf[769]: Dependencies resolved. dnf[769]: Error: The operation would result in removing the following protected packages: dnf, systemd. systemd[1]: dnf-system-upgrade.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: dnf-system-upgrade.service: Failed to load environment files: No such file or directory systemd[1]: dnf-system-upgrade.service: Failed to run 'stop-post' task: No such file or directory systemd[1]: dnf-system-upgrade.service: Unit entered failed state. audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dnf-system-upgrade comm="systemd" exe="/usr/lib/systemd" hostname=? addr=? terminal=? res=failed' systemd[1]: dnf-system-upgrade.service: Failed with result 'resources'. systemd[1]: Rebooting as result of failure.
When I tried distro-sync with --allowerasing, I encounter the exact same error. I found a similar unresolved bug report (with incomplete information), but no other results turned up from a quick search. Any thoughts?
The same happened to me too. F21->f22 upgrade went fine but when updating from F22 to F23 I was not able to boot into system upgrade splash screen. Maybe it's related to this [1] bug report.
Honza
Hi , I had the same experience : I think the only solution of this problem , when it occurs , is a fresh install of Fedora 23 and a lot of irritation.
bye,
Ger van Dijck.
Hi,
On Wed, Feb 03, 2016 at 12:47:33PM +0100, Ger van Dijck wrote:
Op Wed, 03 Feb 2016 11:08:45 +0100 schreef Honza Šilhan
The same happened to me too. F21->f22 upgrade went fine but when updating from F22 to F23 I was not able to boot into system upgrade splash screen. Maybe it's related to this [1] bug report.
My partition had plenty of space. I think it fell into some kind of dependency resolution loop because of not realising that the older versions of dnf and systemd need not be protected.
I had the same experience : I think the only solution of this problem , when it occurs , is a fresh install of Fedora 23 and a lot of irritation.
I managed to fix everything by removing all the old versions of the regular packages using distro-sync --allowerasing, and then removing the protected versions with simple dnf erase. During the upgrade the kernel packages failed half way through, so I had to reinstall those using with dnf reinstall, and only kernel-core with rpm -i --force. Everything thing seems in place now.
Fresh install was not an option for me, I have too many things setup. Maybe I should write a kickstart file one of these days, just in case I need it ;).
Not sure how I can file a bug report though, I really needed the laptop, couldn't wait to go through the whole systematic debugging process.
Cheers,
-
Ger van Dijck -
Honza Silhan -
Suvayu Ali