Master branch builds are failing (currently mitigated)

[NotMyFault]

The latest build on the master branch failed, I verified the failure with an empty PR; #341

I don't think the failures affect the release process, given 2.371 released without packaging issues.

19:54:12  TASK [Wait for instance(s) creation to complete] *******************************
19:54:12  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:12  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:12  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:12  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:13  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:13  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:13  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:13  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:13  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:14  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:14  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:14  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:14  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:15  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:15  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:15  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:15  failed: [localhost] (item=None) => {"attempts": 1, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:15  fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
19:54:15  
19:54:15  PLAY RECAP *********************************************************************
19:54:15  localhost                  : ok=8    changed=4    unreachable=0    failed=1    skipped=2    rescued=0    ignored=0
19:54:15  
19:54:15  WARNING  Retrying execution failure 2 of: ansible-playbook --inventory /home/jenkins/.cache/molecule/Packaging_packaging_PR-341/default/inventory --skip-tags molecule-notest,notest /home/jenkins/workspace/Packaging_packaging_PR-341/venv/lib/python3.8/site-packages/molecule_docker/playbooks/create.yml
19:54:15  CRITICAL Ansible return code was 2, command was: ['ansible-playbook', '--inventory', '/home/jenkins/.cache/molecule/Packaging_packaging_PR-341/default/inventory', '--skip-tags', 'molecule-notest,notest', '/home/jenkins/workspace/Packaging_packaging_PR-341/venv/lib/python3.8/site-packages/molecule_docker/playbooks/create.yml']
19:54:15  WARNING  An error occurred during the test sequence action: 'create'. Cleaning up.
19:54:15  INFO     Running default > cleanup
19:54:15  WARNING  Skipping, cleanup playbook not configured.
19:54:15  INFO     Running default > destroy

[basil]

https://github.com/ansible-community/molecule-docker/releases/tag/v2.1.0 was released only three days ago and included some changes to the code in question in ansible-community/molecule-docker#169 and ansible-community/molecule-docker#170 that probably caused a regression. An issue needs to be reported to the molecule-docker developers, and the version of molecule-docker needs to be pinned back to 2.0.0 in the meantime.

[NotMyFault]

I've pinned the image to 2.0.0 on our end, but I'd like to keep the issue open until the issue is resolved on upstream, see the link.

[basil]

Now that molecule-docker has been deprecated in favor of molecule-plugins, the dependency on molecule-docker needs to be changed to a dependency on molecule-plugins[docker]==23.0.0; otherwise, Dependabot will never offer us any future updates to Molecule.

[NotMyFault]

Good catch! I didn't notice the repository has been archived.

[basil]

Thank you for taking this all the way to the finish line Alex; it is highly appreciated.