Devuan VM: cloud-init OpenRC stage-name drift — cloud-config needs non existent service cloud-init (VM-R6) #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
First-stage Devuan VM image (cloud-init 25.1.4) boots into:
Service 'cloud-config' needs non existent service 'cloud-init'.Cause
Upstream split/renamed the cloud-init systemd stages — the network stage
cloud-init.servicebecamecloud-init-network.serviceand a newcloud-init-main.serviceorchestrator was added — but the OpenRC stageshims (
sysvinit/openrc/) kept the legacy namecloud-init. On an image whoseunits/shims reference the renamed service, OpenRC can't resolve the dependency
and aborts the stage at boot.
Fix (done — research/cloud-init-devuan patch 0004)
provide cloud-init cloud-init-network.cloud-configordersafterboth names.after/beforeonly — no hardneed, so a missing optional stagenever aborts boot.
Build-integration rule (action for the VM build)
A Devuan VM image MUST install the patched OpenRC shim set
(
cloud-init-local cloud-init cloud-config cloud-final) andrc-updateit —do NOT rely on the distro cloud-init package's stale (systemd-era) OpenRC
wiring, which is what produced the boot error.
Status
Fixed in branch
feat/vm-track-and-cloudinit-plans(patch 0004, docs updated).Still needs end-to-end re-test on a rebuilt Devuan VM image (stage 2). Related:
qemu-vm-plan.md "Stage-1 build outcomes".