Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use makefile for molecule tests in CI/CD #309

Merged
merged 2 commits into from
May 2, 2023
Merged

Conversation

vitabaks
Copy link
Owner

@vitabaks vitabaks commented May 2, 2023

Ensure consistency between the development environment and CI/CD tests.

Related PR: #305

@vitabaks
Copy link
Owner Author

vitabaks commented May 2, 2023

https://github.com/vitabaks/postgresql_cluster/actions/runs/4860842570/jobs/8665154692?pr=309

AttributeError: 'Runtime' object has no attribute 'exec'
make: *** [.config/make/molecule.mak:4: molecule-test] Error 1
Error: Process completed with exit code 2.

@ThomasSanson do you have any idea why it doesn't work?

@vitabaks vitabaks self-assigned this May 2, 2023
@vitabaks vitabaks changed the title Use makefile for molecule tests Use makefile for molecule tests in CI/CD May 2, 2023
@ThomasSanson
Copy link
Contributor

@vitabaks
Unfortunately, I don't have any idea why you are getting this error. However, I will investigate the issue to help you resolve it.

I will increased the verbosity to obtain more information.

@ThomasSanson
Copy link
Contributor

@vitabaks

Warning: There is an improperly handled breaking change in ansible-compat, which causes a malfunction in molecule. As a result, you should enforce the usage of ansible-compat==3.0.1 instead of version 4.0.1 (at least until the necessary fix is provided in molecule ansible/molecule#3904 ).

To apply this version fix, add the following line to the requirements.dev.txt files :
ansible-compat==3.0.1

Additionally, this issue serves as another reason why I advocate for freezing the versions of dependencies – all versions, in fact.

There is an improperly handled breaking change in ansible-compat, which causes a malfunction in molecule. As a result, you should enforce the usage of ansible-compat==3.0.1 instead of version 4.0.1 (at least until the necessary fix is provided in molecule ansible/molecule#3904 ).
@vitabaks
Copy link
Owner Author

vitabaks commented May 2, 2023

@ThomasSanson Thank you so much for your help!

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