Hi,
after a normal CLI run with update the summary mail only contained this:
Ultimate Updater update summary
Nodes:
Guests:
β
π§ 100 Β· vm01
Up to date
No nodes and none of the other guests. EMAIL_SINGLE_RUNS is false.
status.json right after the run only holds one target (reproducible, before the run it had 16):
$ ultimate-updater check # status.json: 16 targets
$ update
2026-09-21T18:15:12Z
vm 100 ok success
I think the cause is in UPDATE_CHECK in update.sh. Host and container post-update checks run with STATUS_MODEL_PARTIAL=true, but the VM branch doesn't:
elif [[ "$CVM" == true ]]; then
ssh -q -p "$SSH_PORT" "$HOSTNAME" "\"$LOCAL_FILES/check-updates.sh\" -u cvm \"$VM\"" | tee -a $LOCAL_FILES/check-output
So check-updates.sh finishes non-partial and STATUS_MODEL_FINISH replaces the whole file with just that VM record. VMs are updated after the containers, so the last VM is the only thing left. The mail (UPDATE_MAIL_BODY -> STATUS_MODEL_RENDER_NOTIFICATION) and the Web UI then work from that reduced file.
Probably enough to pass the flag like in the other branches, e.g.
ssh -q -p "$SSH_PORT" "$HOSTNAME" "STATUS_MODEL_PARTIAL=true \"$LOCAL_FILES/check-updates.sh\" -u cvm \"$VM\""
or call it locally without ssh like the host/container branches do.
Version:
Version overview (develop)
Installed commit: 36d32e09ce05e3e6e174f47bef73399c75773b92
Available commit: 36d32e09ce05e3e6e174f47bef73399c75773b92
Installed tag: β
Component Local Server
--------- ----- ------
Updater 5.1.3 5.1.3
Extras 3.1 3.1
Config 2.1 2.1
Welcome 3.0 3.0
Check 2.1 2.1
Running ultimate-updater check afterwards restores everything.
Hi,
after a normal CLI run with
updatethe summary mail only contained this:No nodes and none of the other guests. EMAIL_SINGLE_RUNS is false.
status.json right after the run only holds one target (reproducible, before the run it had 16):
I think the cause is in UPDATE_CHECK in update.sh. Host and container post-update checks run with STATUS_MODEL_PARTIAL=true, but the VM branch doesn't:
So check-updates.sh finishes non-partial and STATUS_MODEL_FINISH replaces the whole file with just that VM record. VMs are updated after the containers, so the last VM is the only thing left. The mail (UPDATE_MAIL_BODY -> STATUS_MODEL_RENDER_NOTIFICATION) and the Web UI then work from that reduced file.
Probably enough to pass the flag like in the other branches, e.g.
or call it locally without ssh like the host/container branches do.
Version:
Running
ultimate-updater checkafterwards restores everything.