[Bug Report] In cluster mode， cubemastercli template redo tpl to compute node ，pmem file artifact sha256 mismatch

[lifehacking]

Summary

cubemaster in ha mode(two master node, three compute node )，in one master node ，cubemastercli template redo --node xxx --template-id xxx sync tpl to compute node，return error msg：

2026/07/17 13:54:16 template image job failed template_id=tpl-71f7ca1c1bb34a8e9e496e3a job_id=2171ef30-c26f-4232-afa4-84e3aee86ec4 artifact_id=rfs-138f433f5ccb04a2e879707d distribution=0/1 ready, 1 failed error=artif
act redistribution failed on all 1 nodes: cubelet create image on 10.228.161.14 failed: pull image rfs-138f433f5ccb04a2e879707d: ensure pmem file failed: pmem file /usr/local/services/cubetoolbox/cubebox_os_image/rfs
-138f433f5ccb04a2e879707d/rfs-138f433f5ccb04a2e879707d.ext4 not exist and download failed: artifact sha256 mismatch, got 6024f9ffe5ac059406b8f91e4046fc82bb62d9e08a64d0c337338dfdd3309ed6 want 189ef958159a1b98b00173a98
9d007f659d047bae4586d3a80d7e29d50486195
cubemastercli run fail: artifact redistribution failed on all 1 nodes: cubelet create image on 10.228.161.14 failed: pull image rfs-138f433f5ccb04a2e879707d: ensure pmem file failed: pmem file /usr/local/services/cub
etoolbox/cubebox_os_image/rfs-138f433f5ccb04a2e879707d/rfs-138f433f5ccb04a2e879707d.ext4 not exist and download failed: artifact sha256 mismatch, got 6024f9ffe5ac059406b8f91e4046fc82bb62d9e08a64d0c337338dfdd3309ed6 w
ant 189ef958159a1b98b00173a989d007f659d047bae4586d3a80d7e29d50486195

/data/CubeMaster/storage/ already sync in master nodes

Environment

• CubeSandbox version / commit: 0.5.1 / a164417
• Host OS and kernel version: ubuntu22.04 / 6.6.69-opencloudos9
• KVM info (modinfo kvm):
• Deployment mode: cluster
• Relevant component:

[cubesandboxbot]

This issue might be related to an existing issue. Please check:

• Cubemaster loses local artifact files after Pod restart while artifact metadata remains READY #852: "Cubemaster loses local artifact files after Pod restart while artifact metadata remains READY" — describes the same SHA256 mismatch error pattern when the Cubemaster's local artifact storage is out of sync with its metadata. In your case, the mismatch is between a non-empty SHA hash (got 6024f9ffe5... want 189ef958...) rather than an empty-file hash, but the error path and symptoms are nearly identical. Your HA setup with two masters may be triggering a variant of the same underlying artifact-consistency issue.

If this is a different bug, please add more details about what distinguishes it from #852 so a maintainer can triage accordingly.