I see the final stage completing in the log:
journalctl | grep "final: SUCCESS"
Sep 15 12:37:26 yakkety-test-not-finalizing-cloud-init cloud-init[1450]: [CLOUDINIT] handlers.py[DEBUG]: finish: modules-final: SUCCESS: running modules for final
Yet I don't get /var/lib/cloud/instance/boot-finished created.
My case seems to match Martins second finding that cloud-init.target seems to be inactive.
systemctl status cloud-init.target
● cloud-init.target - Cloud-init target
Loaded: loaded (/lib/systemd/system/cloud-init.target; static; vendor preset: enabled)
Active: inactive (dead)
Running into the same since today.
Seems alto reproducible with uvtool.
uvt-kvm create --memory 2048 --cpu 4 --password=ubuntu yakkety- test-not- finalizing- cloud-init release=yakkety arch=amd64 label=daily
I see the final stage completing in the log: test-not- finalizing- cloud-init cloud-init[1450]: [CLOUDINIT] handlers.py[DEBUG]: finish: modules-final: SUCCESS: running modules for final
journalctl | grep "final: SUCCESS"
Sep 15 12:37:26 yakkety-
Yet I don't get /var/lib/ cloud/instance/ boot-finished created.
My case seems to match Martins second finding that cloud-init.target seems to be inactive. system/ cloud-init. target; static; vendor preset: enabled)
systemctl status cloud-init.target
● cloud-init.target - Cloud-init target
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
OTOH - The cloud-final.service looks good: system/ cloud-final. service; enabled; vendor preset: enabled) /usr/bin/ cloud-init modules --mode=final (code=exited, status=0/SUCCESS) slice/cloud- final.service
● cloud-final.service - Execute cloud user/final scripts
Loaded: loaded (/lib/systemd/
Active: active (exited) since Thu 2016-09-15 12:37:26 UTC; 2min 20s ago
Process: 1450 ExecStart=
Main PID: 1450 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 276.0K
CPU: 1.654s
CGroup: /system.