Description of problem: Trying to upgrade F19 to F20 using fedup. On the upgrade reboot it hangs: ............ Reached target Initrd Default Target systemd-journal1d166]: Received SIGTERM systemd[1]: Failed to initialize SELinux context: no such file or directory Version-Release number of selected component (if applicable): Trying to upgrade F19 to F20 using fedup. On the upgrade reboot it hangs: ............ Reached target Initrd Default Target systemd-journal1d166]: Received SIGTERM systemd[1]: Failed to initialize SELinux context: no such file or directory How reproducible: run fedup. reboot Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: grep ^SELINUX /etc/selinux/config SELINUX=permissive I have no encrypted partitions I have no separate /var partition. df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda7 34950848 10675492 22476908 33% / devtmpfs 1530948 0 1530948 0% /dev tmpfs 1536896 132 1536764 1% /dev/shm tmpfs 1536896 800 1536096 1% /run tmpfs 1536896 0 1536896 0% /sys/fs/cgroup tmpfs 1536896 8 1536888 1% /tmp /dev/sda5 487652 123265 334691 27% /boot I was able to get fedup up to run on reboot by installing selinux-policy-targeted , BUT, on reboot it failed after installing about 600 of the 1800 packages. I found the machine powered off. It came up under 19, but full of dupes. By running fedup --clean and fedup --network I found 1200 packages still to be installed.
(In reply to sean darcy from comment #0) > Description of problem: > Trying to upgrade F19 to F20 using fedup. On the upgrade reboot it hangs: > > ............ > Reached target Initrd Default Target > systemd-journal1d166]: Received SIGTERM > systemd[1]: Failed to initialize SELinux context: no such file or > directory [...] > I was able to get fedup up to run on reboot by installing > selinux-policy-targeted Did this message appear? systemd[1]: Failed to load SELinux policy. Freezing. If so, then the missing selinux-policy-targeted was probably the culprit. Otherwise, something else was probably going on.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days