-
Notifications
You must be signed in to change notification settings - Fork 317
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
Fix ubuntu 22.04 molecule test to actually run on 22.04 #594
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! 👍
Unfortunately, CI is failing because jammy
doesn't have a python
package (it was renamed to python3
). We'll need to adapt Dockerfile.j2
in this change.
I believe that |
@nre-ableton Could you please trigger CI again? The way how workflows are set up prevent them from running in my forked branch. |
If I read build log correctly, it fails with |
That's just a warning. The build fails here:
|
Oh, didn't notice that because it was collapsed. Now using python3-apt instead of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix @slonopotamus! 👍
* upstream/master: Remove deprecated molecule/centos-stream-8 Fix rolling restart by waiting for consul leave and after restart Update molecule.yml --- (ansible-collections#597) Bump idna from 3.3 to 3.7 in the pip group across 1 directory (ansible-collections#596) Fix CI badge in README (ansible-collections#595) Fix ubuntu 22.04 molecule test to actually run on 22.04 (ansible-collections#594) feat: Configuration validation. fix ansible-collections#518 (ansible-collections#592) Fix error when creating gossip key (ansible-collections#558) adding become to service restarts (ansible-collections#571) Bump the pip group across 1 directories with 1 update (ansible-collections#590)
SUMMARY
molecule/ubuntu-22.04/molecule.yml
used 20.04 instead of 22.04, this definitely was not intended.ISSUE TYPE