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

Ansible Molecule E2E is failing in CI #6433

Closed
everettraven opened this issue May 16, 2023 · 3 comments
Closed

Ansible Molecule E2E is failing in CI #6433

everettraven opened this issue May 16, 2023 · 3 comments
Assignees
Labels
priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-blocker This issue blocks the parent release milestone
Milestone

Comments

@everettraven
Copy link
Contributor

Bug Report

The ansible molecule e2e test is failing in CI

What did you do?

Action was run as part of CI on a PR

What did you expect to see?

The test to pass

What did you see instead? Under which circumstances?

The test appears to be failing due to an AttributeError that is likely the result of some python dependency change. Here is a failing CI run as an example: https://github.com/operator-framework/operator-sdk/actions/runs/4992572478/jobs/8940466410?pr=6425

@varshaprasad96 varshaprasad96 added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 22, 2023
@varshaprasad96 varshaprasad96 added the release-blocker This issue blocks the parent release milestone label May 22, 2023
@varshaprasad96 varshaprasad96 added this to the v1.29.0 milestone May 22, 2023
@grokspawn
Copy link
Contributor

upstream ansible issue: ansible/molecule#3903

@tonyskapunk tonyskapunk mentioned this issue May 22, 2023
2 tasks
@tonyskapunk
Copy link
Contributor

👋 Hi @grokspawn I also saw the issue locally where I use python 3.11. I found out that the GHA was not using the expected python version (3.8) I created a change #6444 that should get it going, would you mind giving it a look?

Thanks!

@everettraven
Copy link
Contributor Author

Closing this issue since the fix by @tonyskapunk has resolved this. Thanks so much @tonyskapunk !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-blocker This issue blocks the parent release milestone
Projects
None yet
Development

No branches or pull requests

4 participants