Run the deploy job on a systemd node - #40
Merged
Merged
Conversation
Provisioning failed once it reached the application layer:
System has not been booted with systemd as init system (PID 1).
Can't operate. Failed to connect to bus: Host is down
cloudmon deploys through systemd -- 15 unit templates, 68 systemd tasks and 14
daemon_reload calls -- so the node needs a real init. Switch the nodeset to the
new zuul-debian-systemd label, which runs systemd as PID 1.
With systemd present, let it own containerd and dockerd instead of starting
them with nohup; hand-started daemons would collide with the units the
cloudmon roles enable. The daemon settings now come from /etc/docker/daemon.json
seeded by the pod spec. Diagnostics read the journal instead of the log files
the manual start used to write.
Verified on a probe pod on the cluster: PID 1 is systemd, is-system-running
reports running, daemon-reload succeeds, and a unit written at runtime can be
enabled and started.
vladimirhasko
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #38 and #39.
Provisioning now reaches the application layer (
ok=25 changed=14) and fails there:This is not a missing package. cloudmon deploys through systemd:
systemdmodule tasksservicemodule tasksdaemon_reloadcalls*.service.j2unit templatessystemd has to be PID 1, which cannot be arranged after a container starts, so gating those tasks would make the job green while deploying nothing. Instead the job moves to a node that has a real init.
Infra side (
opentelekomcloud-infra/system-config): newzuul-debian-systemdlabel and image — systemd as PID 1, privileged,/sys/fs/cgroupwritable (the cluster is cgroup v1), tmpfs on/run. Pinned to the HCE 5.10 nodes, because bookworm's systemd 252 will not run on the CentOS 7 nodes' 3.10 kernel.zuul-debian-dockeris untouched, sincezuul-infra's smoke test uses it.This PR: point the nodeset at the new label, and let systemd own containerd/dockerd instead of
nohup. Hand-started daemons would collide with the units the cloudmon roles enable. Daemon settings (MTU 1442,bridge: none,iptables: false, cgroupfs driver) move into/etc/docker/daemon.json, seeded by the pod spec. Diagnostics read the journal.Verified on a probe pod on the cluster before changing the job: