Hide Forgot
Description of problem: When I try to create and test a simple scenario molecule failed when it try to destroy the instance Version-Release number of selected component (if applicable): python3-molecule-2.19-2.fc29.noarch How reproducible: Always Steps to Reproduce: dnf install python3-molecule yamllint python3-ansible-lint docker -y molecule init role -r dummy cd dummy molecule test Actual results: Command failed with: ... --> Scenario: 'default' --> Action: 'destroy' ERROR! the playbook: None could not be found ERROR: An error occurred during the test sequence action: 'destroy'. Cleaning up. --> Scenario: 'default' --> Action: 'destroy' ERROR! the playbook: None could not be found ERROR: Expected results: command finish with error Additional info: On https://github.com/ansible/molecule/tree/master/molecule/provisioner there is an ansible directory which containts create.yml and destroy.yml for docker, lxc and vagrant. Adding this directory on /usr/lib/python3.7/site-packages/molecule/provisioner/ fix the issue (the job failed, but I didn't debug yet) ... --> Scenario: 'default' --> Action: 'destroy' PLAY [Destroy] ***************************************************************** TASK [Destroy molecule instance(s)] ******************************************** changed: [localhost] => (item=None) changed: [localhost] Thanks
I confirm that there is a missing folder for the provisioning drivers. Had to copy it manually from a virtual environment to get molecule working again. sudo cp -r ~/.cache/virtualenv/molecule/lib/python3.7/site-packages/molecule/provisioner/ansible/ /usr/lib/python3.7/site-packages/molecule/provisioner/ tree ~/.cache/virtualenv/molecule/lib/python3.7/site-packages/molecule/provisioner/ansible/ ~/.cache/virtualenv/molecule/lib/python3.7/site-packages/molecule/provisioner/ansible/ ├── playbooks │ ├── docker │ │ ├── create.yml │ │ └── destroy.yml │ ├── lxd │ │ ├── create.yml │ │ ├── destroy.yml │ │ └── prepare.yml │ └── vagrant │ ├── create.yml │ └── destroy.yml └── plugins ├── filters │ ├── molecule_core.py │ └── __pycache__ └── libraries ├── molecule_vagrant.py └── __pycache__
Created attachment 1535524 [details] spec file
Created attachment 1535525 [details] adding support for resources files in the python build
Quick update: after some fiddling, I found the issue with the missing files. The %prep stage that executes python2 setup.py build '--executable=/usr/bin/python2 -s' fails to capture the ansible folder under provisionner because it's not a python module. So the solution is the change the setup.py and add a Manifest.in file to force it to do so. the details are in this issue https://github.com/ansible/molecule/issues/1753 the dev team at molecule were favourable to my proposed changes. So now we will just have to wait for them to review and bump the version. as for the fedora side, I uploaded a modified spec file and a patch that fix this issue to, so it's up to the packager to rebuild them.
FEDORA-2019-95a631828d has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-95a631828d
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug applies for Fedora 30, and so far as I can tell for Fedora 31 as well. Please fix promptly. It is not necessary to move to 2.22 if that's what is holding things back. The same fix applies for 2.20.1 of the molecule code as built with 4bf5f65 from the Fedora Sources python-molecule repository on Fedora 30.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
FEDORA-2020-da7af6e03f has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-da7af6e03f
FEDORA-2020-0c221024ae has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0c221024ae
FEDORA-2020-fd94e0d12d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd94e0d12d
FEDORA-2020-0c221024ae has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0c221024ae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0c221024ae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fd94e0d12d has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fd94e0d12d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd94e0d12d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-da7af6e03f has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-da7af6e03f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-da7af6e03f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fd94e0d12d has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-0c221024ae has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.