Chris Musty's picture

S3DataError: BotoClientError: ETag from S3 did not match computed MD5

OK So here is the scenario.

Bunch of vm's running on a server under proxmox.

Firewall kicks the bucket so I decide to swap it out for clearos (not too bad).

Ever since then I get the error message above, here it is again

S3DataError: BotoClientError: ETag from S3 did not match computed MD5

Firstly WTF

Secondly I tried to force a tklbam-init over to another hub account and it also fails.

Any ideas? Google is not being helpful!

Forum: