Several Issues in usage and documentation

[provenvelocity]

I know this is unusual and I am sorry but just closing the tickets and not even letting me retest and then not responding to the retests is really frustrating... I am trying to help your code and only file things after deep testing. Yes, I tested with one minor version back but they are still issues, and closing them prior to at least let me test in them in the latest is rude and not a part of the good conduct pact all ansible projects take part in.

The first issue is minor but confusing and still occurs even in the latest code.
#3131

The second issue is a bigger issue and still takes place in the latest also. I still cannot get a playbook from a collection to converge and in working on this issue I found each step in your code is making its own custom env and not respecting things like env.yml in some or custom collection_path or ansible_colection_path .... I need to make a feature request probably in the end to improve the environment configuration code, but either way, you cant converge playbooks from collections.

This could be that the collections path is wrong in the provision part of the code ignoring the ansible-lint collections path... I'm not sure yet.

Also I'm working with Redhat and ansible to see if it's even a bigger issue than just your code. I think the issue is not what I thought in the end but it is all linked and the outcomes in the ticket is still the same that there is an issue in both molecule and ansible with running collection playbooks...

#3135

If I'm wrong in the end then I am sorry but I would rather be wrong and know why than be just shut down and ignored...

[ssbarnea]

Please do not abuse the issue tracker and use it only when a bug is very clear to reproduce. The reason I closed both bugs is because they failed to describe the issue at the start and also being very verbose. Instead of adding more comments is often better to edit initial report and to avoid putting too long pasted in it (these being better in gists).

Keep in mind that nobody involved with this project is paid to maintain it and we all have very limited time. Closing them is an ack that they are not really clear.

Closing bugs does not prevent others from commenting them, is not locking, something we probably never had to do with molecule.

How about creating a minimal git repository where you can reproduce the bug running molecule, one that has everything that is not needed taken away? I used this approach from time to time in order to demonstrate bugs.

We all can be wrong, please be patient. Understand that maintainers can often hardly be able to keep-up with reviewing PRs that pass testing, dealing with bugs is.

Try to find me on our irc channel, I may be able to help you there, being more interactive.

[provenvelocity]

I have outlined all the issues I am having and since my issues keep getting closed I put them all here and am not going to open new ones until we get a good working relationship. I have been an eng for 25 plus years and DevOps for 90% of prior to it being a thing.... I am working to convert a large company to ansible and molecule and need many of these things fixed for them to use molecule. I will contribute to the code if and when again we have a working relationship. the code is all set up just follow the steps and use the branch to test... thanks https://github.com/provenvelocity/devops_test

[provenvelocity]

The import_playbook issue is actually a molecule issue, not an ansible issue. I went back and forth with them and was able to isolate it to molecule.

ansible/ansible#74917

[provenvelocity]

@ssbarnea The issue comes back to the fact that the molecule does not have the ansible lint collections path in the collections path folder and since it uses ansible-lint to manage the installation of the roles and collections you need that path.

I was able to override the collections paths and also I had to monkey patch the ansible lint code to allow an override on the cache dir it uses and then it all worked. though this is not a long-term workaround or fix due to the monkey patch needed to fix it.