Notifications: name the image, and tell a capture from a deploy (#21).
The six imaging listeners registered for HOST_IMAGEUP_COMPLETE and HOST_IMAGE_FAIL and then ignored which event had arrived, so a finished capture announced itself identically to a deploy and a failure said This host has failed to image with no hint as to why.
| before | after | |
|---|---|---|
| deploy | Host lab01 completed imaging. | Host lab01 finished deploying image Win11-Lab. |
| capture | Host lab01 completed imaging. | Host lab01 finished capturing image Win11-Lab. |
| failure | Host lab01 imaging failed. | Host lab01 failed imaging Win11-Lab: fog.download: failed to restore partition 2 … |
The failure case is the one worth updating for. The FOS reporting work (FOGProject/fogproject#1206, #1211, #1217, #1223) gives a failed task a stored, multi-line report of what FOS actually said — and until this release none of it reached a notification. Verified live before the release: a report whose stored row read fog.download: failed to restore partition 2 / partclone.ntfs: /dev/sda2 is busy / … pushed only Failed / This host has failed to image.
Every added key is read defensively, with a translated placeholder for a missing one, so all six keep working against a server whose core still sends nothing but HostName — they just say more on one that has taken FOGProject/fogproject#1205.
fog_min is unchanged for that reason.
Requires core with FOGProject/fogproject#1205 to carry the image name and the failure reason. The 1.5 equivalent is FOGProject/fogproject#1226.