Bug 727404
| Summary: | systemd unit files missing from install image | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Reiser <jreiser> | ||||||||||||
| Component: | lorax | Assignee: | Brian Lane <bcl> | ||||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 19 | CC: | anaconda-maint-list, bcl | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2013-10-30 17:56:52 UTC | Type: | --- | ||||||||||||
| 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
John Reiser
2011-08-02 03:54:42 UTC
Can you please attach the pylorax.log ? You can find it in the pungi work directory. Created attachment 516372 [details] pylorax.log Here is pylorax.log from my pungi run which finished just now. It looks to be of no use here, because my composes still fail due to bug #726743 (pyorbit missing). I'll keep trying. Created attachment 516401 [details]
pylorax.log.gz
This pylorax.log (gzipped) is from a pungi run that succeeded. However the previous complaints from systemd during boot of DVD for install have gone away. Instead there are now multiple avc's related to systemd. I'll see what happens tomorrow morning.
Created attachment 516545 [details]
pylorax.log.gz
From a pungi DVD that was built using today's f16-branched repo.
Created attachment 516546 [details]
/tmp/syslog during install
Here is the syslog from an install of a DVD corresponding to that pylorax.log.gz. Several systemd unit files are missing (lines 891-909). Also there are many avc complaints (lines 732-740, 818, 864-879, etc.) Either lorax forgot the files and/or their selinux security context labels, or dracut didn't re-label them correctly during boot, or ...
Created attachment 516547 [details] /tmp/syslog with "enforcing=0" This is syslog from the same DVD as before (pylorax.log.gz attachment 516545 [details]; syslog attachment 516546 [details]) except I added " enforcing=0" to the kernel boot command line when installing. The errors are different, including the anaconda error which terminated the install. Does this still happen with f16-alpha? Yes, this still occurs with f15-alpha-x86_64: ----- [from /tmp/syslog during install from DVD] 17:21:12,648 INFO kernel:[ 25.815069] No iBFT detected. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit fedora-storage-init.service, ignoring: Unit fedora-storage-init.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-storage-init.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit fedora-readonly.service, ignoring: Unit fedora-readonly.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-readonly.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit fedora-wait-storage.service, ignoring: Unit fedora-wait-storage.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-wait-storage.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit systemd-remount-api-vfs.service, ignoring: Unit systemd-remount-api-vfs.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-remount-api-vfs.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit avahi-daemon.socket, ignoring: Unit avahi-daemon.socket failed to load: No such file or directory. See system logs and 'systemctl status avahi-daemon.socket' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit dm-event.socket, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit ip6tables.service, ignoring: Unit ip6tables.service failed to load: No such file or directory. See system logs and 'systemctl status ip6tables.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit iptables.service, ignoring: Unit iptables.service failed to load: No such file or directory. See system logs and 'systemctl status iptables.service' for details. 17:21:17,0 NOTICE dbus: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service' 17:21:17,0 WARNING systemd: Cannot add dependency job for unit fedora-storage-init.service, ignoring: Unit fedora-storage-init.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-storage-init.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit fedora-readonly.service, ignoring: Unit fedora-readonly.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-readonly.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit fedora-wait-storage.service, ignoring: Unit fedora-wait-storage.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-wait-storage.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit systemd-remount-api-vfs.service, ignoring: Unit systemd-remount-api-vfs.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-remount-api-vfs.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit avahi-daemon.socket, ignoring: Unit avahi-daemon.socket failed to load: No such file or directory. See system logs and 'systemctl status avahi-daemon.socket' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit dm-event.socket, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit ip6tables.service, ignoring: Unit ip6tables.service failed to load: No such file or directory. See system logs and 'systemctl status ip6tables.service' for details. 17:21:17,0 WARNING systemd: Cannot add dependency job for unit iptables.service, ignoring: Unit iptables.service failed to load: No such file or directory. See system logs and 'systemctl status iptables.service' for details. ----- Typo in previous comment; it is the just-released Fedora 16 alpha, not "f15-alpha-x86_64". This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 If this is still a problem please reopen with current logs from f20. |