I am new to SCM/comply. I am trying to run puppet agent on some hosts I want to be scanned, but they are complaining about a checksum mismatch on Assessor-CLI-4.43.0.zip. Anybody have any thoughts on that? Notice: /Stage[main]/Comply:ScannersCiscat/Exec[Assessor CLI 4.43.0.zip]/returns executed successfully (corrective) Error: Download file checksum mismatch (expected: b165c4fda3bfa1dccd5d17016486f2207b5842c46aecbb8807b1a47552a5e229 actual: 9f88ff4faa3b9ae03a95c2dfb4d84ada7c8daf07f2622be1149d4447719c383d) Error: /Stage[main]/Comply:ScannersCiscat/Archive[Assessor CLI 4.43.0.zip]/ensure change from (sha256)9f88ff4faa3b9ae03a95c2dfb4d84ada7c8daf07f2622be1149d4447719c383d to (sha256)b165c4fda3bfa1dccd5d17016486f2207b5842c46aecbb8807b1a47552a5e229 failed: Download file checksum mismatch (expected: b165c4fda3bfa1dccd5d17016486f2207b5842c46aecbb8807b1a47552a5e229 actual: 9f88ff4faa3b9ae03a95c2dfb4d84ada7c8daf07f2622be1149d4447719c383d) N I am using version 3.3.0 of the comply module

The checksum in the comply module has a history of not getting updated when the version gets updated. I would recommend checking with support.

good(sad?) to know, thanks

The Comply module and the SCM version you're running must be the same. SCM 3.3.0 includes assessor 4.47.0, so if you're getting an error with 4.43.0, you're either using an older version of SCM or you've hard coded the version somewhere.

could you use version 3.3.1?

@spp mentioned that SCM and the comply module need to be on the same version. While I see a version 3.3.1 of the comply module, SCM only appears to have a 3.3.0 release.

Major/minor needs to be the same.

version 3.3.0 of the comply module was still showing version 4.43.0 for the scanner_version. I updated the module to 3.3.1, the scanner_version now shows 4.47.0 and agent runs are clean 🙂