Skip to content

Feat/molecule-testing#257

Merged
NavidSassan merged 38 commits into
mainfrom
feat/molecule-testing
Jun 9, 2026
Merged

Feat/molecule-testing#257
NavidSassan merged 38 commits into
mainfrom
feat/molecule-testing

Conversation

@ma-benedetti

Copy link
Copy Markdown
Contributor

Implements playbook testing with Molecule

ma-benedetti and others added 30 commits May 15, 2026 12:24
A fully commented, non-functional reference scenario (install + remove sub-scenarios) for the fictional example playbook. It demonstrates how to structure a Molecule test and what to assert: behaviour and end state (service running, the app using the configured value, API-managed state) rather than the role's own mechanics. Copy it as the starting point for a new playbook's test.
- discover VM IPs from the host ARP table (--source arp) instead of the
  DHCP lease table: a stable MAC across recreate cycles accumulates several
  unexpired leases, so --source lease returned stale addresses
- raise the cloud-image download timeout to 120s; the 10s default times out
  when one play pulls all images at once over shared bandwidth
- refresh the apt cache on Debian/Ubuntu during prepare; the cloud images
  ship an empty index, so a bare package install could not resolve anything
- set a known root password on the throwaway VMs for console debugging
Use the ubuntu-lts-latest osinfo alias since libosinfo has no dedicated
26.04 entry yet; it only seeds hardware defaults and tracks the latest LTS.
- drop obsolete accelerate_timeout from config.yml (accelerate plugin was
  removed from Ansible)
- apply | bool to the container privileged/systemd params
- fix the README reference to a non-existent container-create-fail.yml
@NavidSassan NavidSassan merged commit 7358123 into main Jun 9, 2026
11 checks passed
@NavidSassan NavidSassan deleted the feat/molecule-testing branch June 9, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants