-
Notifications
You must be signed in to change notification settings - Fork 37
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
vg_create is not idempotent #132
Comments
It was idempotent earlier, but the commit 0c1f454d98 changed that. But I do not see in the commit message why it was changed. |
@sac , Currently, a lot of oVirt users report issues with this one (for example something failed later and when rerunning it complains the VG exists). |
Also, I don't see peer review on that commit . How is that possible? |
I don't think you should spend time on the PR. The committer should revert his changes unless he has a good reason. We can ask the maintainers to take a look. @rchikatw @gobindadas can you please take a look at this issue? Also, why did a non-idempotent CLI replace the module? |
@sac @hunter86bg |
Because ansible-core 2.12 is no longer used these packages (gluster.gluster and community.general ansible collection) that means they have been removed from RHV packages |
@rchikatw |
This is not the issue only for RHV, it's also issue for centos stream which has ansible-core. So it's a problem for both upstream and downstream. |
So, the modules need to be updated for ansible-core ? |
So basically there are two ways to deal with it. |
@gobindadas , |
For some reason vg_create is using a command that fails if you need to rerun the setup:
gluster-ansible-infra/roles/backend_setup/tasks/vg_create.yml
Line 65 in 6ce7885
We need to use idempotent modules where possible
The text was updated successfully, but these errors were encountered: