molecule: Report failure reason when molecule idempotence runs
Issue Type
- Feature request
Molecule and Ansible details
Latest from pip
Desired Behaviour
When molecule idempotence fails (running molecule converge), the failures should be printed.
Actual Behaviour (Bug report only)
molecule idempotence just reports that some error was encountered during converge.
In order to find out, you then have to run molecule converge again yourself.
This is hiding errors during automated testing, as well as causing molecule converge to be run manually again when used during dev.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 21 (20 by maintainers)
Commits related to this issue
- Display output when `idempotence` fails Fixes: #835 — committed to retr0h/molecule by retr0h 7 years ago
- Forward port idempotence stdout on error Fixes #835 — committed to ansible/molecule by retr0h 7 years ago
- Forward port idempotence stdout on error Fixes #835 — committed to ansible/molecule by retr0h 7 years ago
- V2 promotion (#863) * Init add of molecule v2 work Initial work of a v2 based Molecule. This version of Molecule has a slightly different config, uses Ansible to boostrap the container vs relyi... — committed to ansible/molecule by retr0h 7 years ago
- Raise stdout on idempotence error Need to error with e.stdout vs simply stdout to obtain the entire error message. Fixes: #835 — committed to ansible/molecule by retr0h 7 years ago
I’d recommend to open a new issue for this, this issue has been closed for a few years now.
@MarkusTeufelberger thanks for the great report. I have corrected this @ b2495b0bb4984022b15420ccc9e37a531b504834.