Bug 1060595
| Summary: | upgrade hangs on boot: global name 'log' is not defined | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | toddb | ||||||
| Component: | fedup | Assignee: | Will Woods <wwoods> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 19 | CC: | harald, richard.keech, tflink, wwoods, zhangchaowang | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | 980663 | Environment: | |||||||
| Last Closed: | 2014-02-03 17:36:05 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
toddb
2014-02-02 23:41:04 UTC
Well, a bit different. The last three lines (see attached photo for more details) are: [ ok ] Reached target Initrd Default Target. [ 11.895637] systemd-journald[172]: Received SIGTERM [ 12.300643] systemd[1]: Failed to initialize SELinux context: No such file or directory And nothing after that. I do have SELinux disabled (via /etc/sysconfig/selinux). So it would seem there is an assumption in the fedup scripts that SELinux is present. Presumably this bug is because each file on the file system must be labeled with an SELinux context. I have these packages installed (but disabled) policycoreutils-2.1.13-59.fc18.x86_64 setroubleshoot-3.2.3-3.fc18.x86_64 libselinux-python-2.1.12-7.3.fc18.x86_64 selinux-policy-3.11.1-108.fc18.noarch libselinux-2.1.12-7.3.fc18.i686 selinux-policy-doc-3.11.1-108.fc18.noarch libselinux-devel-2.1.12-7.3.fc18.x86_64 selinux-policy-devel-3.11.1-108.fc18.noarch libselinux-utils-2.1.12-7.3.fc18.x86_64 libselinux-2.1.12-7.3.fc18.x86_64 Created attachment 858331 [details]
boot screen during upgrade
Created attachment 858342 [details]
boot screen during upgrade
I have tried re-enabling selinux, but it refuses, probably for a variety of reasons (yes, I updated /etc/sysconfig/selinux to be permissive). # /usr/sbin/load_policy -i SELinux: unable to find usable policy file: No such file or directory /usr/sbin/load_policy: Can't load policy: No such file or directory The log I attached seems similar to #912058, but reviewing comments by wwoods > a) mdraid disks that require mdadm.conf to be configured (bug 895805) I do have mdraid, but I don't believe they need to be configured. It works fine under fedora 18. > b) multiple encrypted partitions (bug 896010) > c) encrypted /home only (bug 894242) > d) old version of systemd in F17 (bug 910326) No, no and no. Could it be that fedup has trouble with lvm on top of md on top of disks? Oh, yes, and I did 'dracut -f' as suggested in #845194. No change. ... and installing a two packages for selinux (listed here: http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html) allowed selinux to be enabled. And that allowed fedup 18-->19 to proceed. So that's the bug: enabled selinux is required for fedup to work. I'm sure there's much more subtlety than that last sentence, but I would hope that someone cares enough to put this on the to-do list. *** This bug has been marked as a duplicate of bug 1044484 *** |