Skip to content
Nodus

SHA256Mismatch

View Markdown

HTTP status: 412 · Retryable: no

A write with expectedSHA256 found different content than the writer started from, so nothing was written.

Message

Section titled “Message”
the file {path} changed: its SHA-256 does not match expectedSHA256

What to do

Section titled “What to do”

read the file again, merge your change, and write it with the new digest as expectedSHA256

On the wire

Section titled “On the wire”

The response is a Kubernetes Status with reason: SHA256Mismatch and code: 412, plus fix, docs (this page) and requestId. details.causes lists the fields involved, when there are any. The CLI prints the fix and the request id; the Python SDK raises nodus.errors.SHA256Mismatch.