Issue Type

• Bug report

Molecule and Ansible details

ansible 2.4.2.0
molecule, version 2.6.0

• Molecule installation method: pip
• Ansible installation method: pip

Desired Behaviour

After upgrading to molecule 2.6.0 I always get the message that it is skipping destroy even though I have not configured --destroy=never. I think the default should be for it to destroy the container unless --destroy=never passed.

Actual Behaviour (Bug report only)

Unless the command is run with --destory=always then it skips the destroy step.

--> Action: 'destroy'
Skipping, '--destroy=never' requested.

Even though --destory=never is not set anywhere. This is from a newly initialized project using the command:

molecule init role --role-name=molecule-upgrade --driver-name=vagrant

The only way to make it run destroy is to pass in --destroy=always or anything besides never.

no-params.log
destroy-always.log