Molecule cleanup failing on Debian Bullseye

[chriscroome]

I'm running molecule in Docker containers via GitLab CI and have this working fine for Debian Bookworm and Trixie and Ubuntu Jammy, the jobs end with:

INFO     Running default > destroy
Molecule default > destroy 00:00
WARNING  Skipping, destroy action has no playbook.
INFO     Pruning extra files from scenario ephemeral directory
Cleaning up project directory and file based variables 00:01
Job succeeded

However on Debian Bullseye they never complete the clean up stage, they only get this far:

INFO     Running default > destroy
Molecule default > destroy 00:00
WARNING  Skipping, destroy action has no playbook.
INFO     Pruning extra files from scenario ephemeral directory

This is with the latest version:

molecule --version

molecule 6.0.1 using python 3.11
    ansible:2.15.3
    azure:23.5.0 from molecule_plugins
    containers:23.5.0 from molecule_plugins requiring collections: ansible.posix>=1.3.0 community.docker>=1.9.1 containers.podman>=1.8.1
    default:6.0.1 from molecule
    docker:23.5.0 from molecule_plugins requiring collections: community.docker>=3.0.2 ansible.posix>=1.4.0
    ec2:23.5.0 from molecule_plugins
    gce:23.5.0 from molecule_plugins requiring collections: google.cloud>=1.0.2 community.crypto>=1.8.0
    podman:23.5.0 from molecule_plugins requiring collections: containers.podman>=1.7.0 ansible.posix>=1.3.0
    vagrant:23.5.0 from molecule_plugins

Doesn't anyone have any suggestions regarding how I could debug and fix this?

[zhan9san]

@chriscroome

I am glad to help you.

Would you mind providing a minimal reproducible example?

Or some related code?

[chriscroome]

Thanks @zhan9san the repo / role in question is this PostgreSQL one the GitLab version is where the CI runs.

I have commented out the Bullesye tests in the gitlab-ci.yml file since this fails as above.

The containers used for testing are built using GitLab CI via this repo and the Docker image that molecule fails to complete in is registry.git.coop/webarch/containers/images/bullseye:20230816, note that this images needs to be run using privileged mode as that is a requirement for systemd in docker.

Is there anything further you can suggest I try to debug this issue?

Should this be turned into a issue rather than a discussion thread?