-
Notifications
You must be signed in to change notification settings - Fork 116
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
Workflow updates #171
Workflow updates #171
Conversation
To note: I'm not sure why the debian 12 job is failing, maybe I haven't done anything to tweak the debian base image as appropriate as I'm using debian:12 whereas previous was using mrlesmithjr/debian:11 ... |
Yes @kwizart - we need another image in https://github.com/mrlesmithjr/dockerfiles/tree/main
|
256cad4
to
0d5fa40
Compare
OK, so I have forced-push to use mrlesmithjr/debian:12 (and defer the fix for a later PR) |
Now we will wait for @mrlesmithjr to merge |
Puzzled about the last Debian 12 fail 🤕 |
I think I found the issue. |
Latest error for Debian 12 is:
If @kwizart doesn't have time I'll try to have a go at it when I'm home! |
For Debian 12 we need: python3-pymysql |
@kwizart - you just need to copy |
Bummer... we're in "OS contribution rabbit whole" :) MariaDB does not build yet for Debian 12. |
...or we could wait a few days - https://jira.mariadb.org/projects/MDEV/versions/29013 - MariaDB 10.6.15 will be released on 2023-07-27 and most probably will also contain a build for Debian 12 (see https://jira.mariadb.org/browse/MDEV-31476). |
I would wait until they build it for Debian 12, doing otherwise may only bring other issues. |
Bummer, the MDEV-31476 was updated: we will not have MariaDB 10.6.x for Debian 12, only MariaDB 10.11.y. @elcomtik && @mrlesmithjr - do we upgrade to MariaDB 10.11 for all or only for Debian 12? What are your thoughts? |
I would upgrade mariadb version for all distros. Role should be updated continuosly and we just need to inform users pin mariadb version in their deployments. |
I've tried to set it in the molecule config for Debian 12 to avoid to bump the default (either defaults/main.yaml or vars/debian-12) as it's probably better for end-users to select the appropriate mariadb_version themselves. Then it should be possible to deprecate having a default mariadb_version set at all. So it will fully defer this choice/responsibility to users. An alternative/possible solution would be to only bump vars/debian-12.yml to a sane default. |
Bumps [cryptography](https://github.com/pyca/cryptography) from 39.0.1 to 41.0.0. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@39.0.1...41.0.0) --- updated-dependencies: - dependency-name: cryptography dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
Centos Stream 8 is another distribution
This fixes the following error from ansible-lint: ... File "/home/runner/.cache/pre-commit/repory1hpslb/py_env-python3.9/lib/python3.9/site-packages/ansible_compat/prerun.py", line 13, in get_cache_dir basename = project_dir.resolve().name.encode(encoding="utf-8") AttributeError: 'str' object has no attribute 'resolve' This is because ansible-lint doesn't support the new api from ansible-compat v4 see also ansible/ansible-compat#258 (comment)
To be fixed at a later point
b3669f2
to
d49f3b6
Compare
I must say I merged even though I don't agree w/ disabling centos8. |
Sorry, but this was never raised. Why do you disagree ? I'm a fedora/EPEL contributor so I'm very interested in centos eco-system itslef. But centos8 is just EOL distro. specially over rocky8 and later. As I said centos stream is a a different thing tought. |
I think bumping should be done at some point, but then there is a need to have a safe guard. I would go with: if early in the role the already installed mariadb version doesn't "start with" the major version set in the ansible variable and ansible_allow_upgrade_major_mariadb is False, then the role should exit early asking to set the mariadb_version. That should prevent any surprise... (I might fill a dedicated ticket/PR for this issue) With that said, I would probably drop the dedicated mariadb_version set in debian-12. I feel uncomfortable with this on a second tough (as I create another place where the version is set instead in the role of global location). Btw, thanks for having merged this PR! |
I have upgraded all CentOS 8 server to CentOS 8 Stream and I haven't felt any difference - of course this is anecdotal evidence but it's the simplest path for those that were and are still on CentOS 8. The image was already moved by @mrlesmithjr to Also we should introduce CentOS 9 Stream. |
So if there is a dedicated centos8stream and centos8stream tests, I'm fine. But having centos8 is miss-leading. |
Not necessarily since everyone knows centos8 was changed into centos8stream. |
Unfortunately no: centos8 (Linux, aka EOL) usage on mirrors are still dramatically high. Properly naming things is not is not a side thing. |
I agree to just disagree on this :) |
* Bump cryptography from 39.0.1 to 41.0.0 * Disable debian9 && centos8 superseeded by rocky8, Centos Stream 8 is another distribution * Bump pre-commit version to current * [molecule] Add debian12 scenario * Add debian-12 vars * [ansible-lint] remove outdated tag * [ansible-lint] Add .ansible-lint-ignore To be fixed at a later point * Add default mariadb version for debian-12 --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This is a workflow update needed to fix the failing distros and pre-commit checks.
Description
Related Issue
NA
Types of changes
Checklist:
Some error where discovered by fixing this ansible-lint: