Details
-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
8.0
-
None
-
XSI-423
Description
3 units are referenced in systemd configuration without actually existing on the system, and one is referenced but masked. This should not be harmful but is at least not clean and could reveal misses in systemd configuration changes for Citrix Hypervisor 8.0.
[root@xs-8-0-sve ~]# systemd-analyze verify default.target Cannot add dependency job for unit getty@tty1.service, ignoring: Unit is masked. Cannot add dependency job for unit qemuback.service, ignoring: Unit not found. Cannot add dependency job for unit dom0term.service, ignoring: Unit not found. Cannot add dependency job for unit display-manager.service, ignoring: Unit not found.
I tracked down the references to these units.
qemuback.service
[root@xs-8-0-sve ~]# grep /etc /usr -r -e "qemuback.service" /etc/systemd/system/xapi.service.d/local.conf:Wants=tapback.service qemuback.service /etc/systemd/system/xapi.service.d/local.conf:After=tapback.service qemuback.service /usr/lib/systemd/system-preset/90-default.preset:enable qemuback.service
There is no such service. Probably those files should be updated?
dom0term.service
[root@xs-8-0-sve ~]# grep /etc /usr -r -e "dom0term.service" /usr/lib/systemd/system-preset/90-default.preset:enable dom0term.service
Idem.
getty@tty1.service and display-manager.service
[root@xs-8-0-sve ~]# grep /etc /usr -r -e "getty@tty1.service" -e "display-manager.service" /usr/lib/systemd/system/plymouth-poweroff.service:After=getty@tty1.service display-manager.service plymouth-start.service /usr/lib/systemd/system/plymouth-reboot.service:After=getty@tty1.service display-manager.service plymouth-start.service /usr/lib/systemd/system/plymouth-kexec.service:After=getty@tty1.service display-manager.service plymouth-start.service /usr/lib/systemd/system/graphical.target:Wants=display-manager.service /usr/lib/systemd/system/graphical.target:After=multi-user.target rescue.service rescue.target display-manager.service /usr/lib/systemd/system/plymouth-halt.service:After=getty@tty1.service display-manager.service plymouth-start.service /usr/lib/dracut/modules.d/98systemd/dracut-shutdown.service:After=getty@tty1.service display-manager.service
These would be more difficult to solve and do not seem to reveal forgotten changes. It would be cleaner if they could be avoided. You decide.
For future releases, I suggest to add this check to your automated pre-release checks:
systemd-analyze verify default.target