8.6.0 (latest) ansible.netcommon is broken when pulling from ansible galaxy

Get Help
, , ,
1

Copied from Latest revision is broken when pulling from ansible galaxy · Issue #797 · ansible-collections/ansible.netcommon (seeing the same on Ansible 2.18.x and 2.19.x).

Anyone know when this might be fixed or what caused it?

SUMMARY

the latest version of this project fails to pull down from ansible galaxy with the following error:
“ERROR! Failed to download collection tar from ‘server0’ due to the following unforeseen error: Mismatch artifact hash with downloaded file”

ISSUE TYPE

  • Bug Report

COMPONENT NAME

the push to galaxy ?

ANSIBLE VERSION
[core 2.15.12]
COLLECTION VERSION
Downloading https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/ansible-netcommon-8.6.0.tar.gz to /var/lib/awx/projects/.__awx_cache/_13__devops_sc_ansible/stage/tmp/ansible-local-16104zj4px7j/tmpyqn3yds6/ansible-netcommon-8.6.0-7sfg7sgz
CONFIGURATION
OS / ENVIRONMENT

AWX runner

STEPS TO REPRODUCE

pull down the latest version from galaxy
EXPECTED RESULTS

should pull down without issue

ACTUAL RESULTS

fails to pull w/ the following error

ERROR! Failed to download collection tar from 'server0' due to the following unforeseen error: Mismatch artifact hash with downloaded file
2

This sounds similar to an issue we had with community.general 13.0.0: Mismatch artifact hash with downloaded file - 13.0.0 · Issue #12082 · ansible-collections/community.general · GitHub

The problem there was that the publish process on Zuul ran more than once in parallel, and apparently a later run uploaded a new tarball, but the checksums were from a previous version of the tarball. (The tarballs’ contents were identical up to timestamps I think, but that’s enough to make the checksum fail.)

The solution was to re-trigger the publishing step once more, and then wait until all mirrors were updated. (It apparently took some time, and then there are client-side caches - see the --no-cache parameter.)

In any case, this needs to be done by someone with appropriate rights for the collection. @KB-perByte maybe you can help?

3

Thanks for reporting this, we will be releasing ansible.netcommon 8.6.1 soon this week

4

ansible.netcommon 8.6.1 is released to galaxy