Skip to content

Prepare ceph-ansible for ansible-core 2.19#7693

Open
damiandabrowski5 wants to merge 2 commits intoceph:mainfrom
damiandabrowski5:ansible-core-2.19
Open

Prepare ceph-ansible for ansible-core 2.19#7693
damiandabrowski5 wants to merge 2 commits intoceph:mainfrom
damiandabrowski5:ansible-core-2.19

Conversation

@damiandabrowski5
Copy link
Copy Markdown

No description provided.

@noonedeadpunk
Copy link
Copy Markdown
Contributor

@clwluvw It would be super helpful if you could trigger the CI run for the change (and review ofc :)) - as we'd love to ensure ceph-ansible works with modern ansible-core.

@github-actions
Copy link
Copy Markdown

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

@github-actions github-actions Bot added the stale label Apr 29, 2026
@noonedeadpunk
Copy link
Copy Markdown
Contributor

It would be really nice to have some review here, as this solves comparability with relevant Ansible versions...

@github-actions github-actions Bot removed the stale label Apr 30, 2026
@badfiles
Copy link
Copy Markdown

badfiles commented May 4, 2026

the tool looks abandoned, issues remain for years and not discussed

i guess a good fork would keep it alive

@noonedeadpunk
Copy link
Copy Markdown
Contributor

I would be open to some forking discussion, tbh. We were discussing it a while back (like 2-3y ago), and there were quite some people still interested in maintaining ceph-ansible.

One my idea could be is to use openinfra as a place where to reside the fork (as it's where I make use of ceph-ansible the most 😅), but it's not using GitHub directly, but Gerrit with a mirror to GitHub. So I am not sure this fork is gonna be visible and discoverable.

I could also use my GitHub "org" to make a fork in there, but then I don't want to make an impression that it's some kind of "internal" fork and ensure that everyone interested can contribute and keep maintenance of the project.

So I would be really open to any kind of suggestions.

@clwluvw
Copy link
Copy Markdown
Member

clwluvw commented May 4, 2026

Sorry for the late reply, I'll try to look at it today. Unfortunately, the CI has been broken for a while, so I need to evaluate it myself. If you are interested in contributing to this project, I'd be happy to review the PRs in a meantime. :)

@noonedeadpunk
Copy link
Copy Markdown
Contributor

I can help out with the CI for sure, that's not a problem. It's just hard to know what is needed for the project, until smth does not work for you, at which point you step in with proposals:)

Signed-off-by: Damian Dabrowski <damian.dabrowski@cleura.com>
@noonedeadpunk
Copy link
Copy Markdown
Contributor

@clwluvw or you mean CI has been broken in terms that main functional jobs are actually never executed/scheduled on the backend? As github actions are actually handling tiny amount of tests, and rest are in some external CI?

As yeah, I can't realistically help with external CI...

@noonedeadpunk
Copy link
Copy Markdown
Contributor

FWIW, I am present in #ceph-ansible channel on ceph-storage Slack... So we can have some discussion there as well, if you prefer:)

Comment thread module_utils/ca_common.py
Previous commit fixes that only in one place, while it turns
out that there are more places containing the incorrect approach.

Signed-off-by: Damian Dabrowski <damian.dabrowski@cleura.com>
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.

4 participants