-
Notifications
You must be signed in to change notification settings - Fork 169
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
repository errors out when trying to update a repository with unsupported flags #975
Comments
as we discussed that before, here for everyone to read: the problem is that the module compares the existing repository to what you told it to create and sees a diff (as seen in the diff output of check mode), but those parameters aren't part of your katello version, so the api-parameter-cleanup step wipes them and we submit an empty json, which the API correctly rejects. |
@pcfe could you do me a favor and test if the issue still persists if you remove the |
nvm, I can repro that on my sat 6.6 and removing okay, now, how do I remove that automatically? |
confirmed, removing |
SUMMARY
Satellite 6.7.3 throws the following on the second run of a task that tries to ensure a repo is present
ISSUE TYPE
ANSIBLE VERSION
KATELLO/FOREMAN VERSION
APYPIE VERSION
STEPS TO REPRODUCE
try to run a playbook containing this task twice (first run works)
EXPECTED RESULTS
since the repo exists from first run, on subsequent runs I would like it to behave as defined by
state:
, so in this case override any manual changes someone might have done in the Satellite webUI.Well and of course I want the playbook to be idempotent. :-)
ACTUAL RESULTS
on runs where the playbook would not need to change anything, I get with -vvv
and with --check --diff I get
additional info
here's the fulll playbook in case you wanna see it. Any comment welcome (just in case I do sth stupid in it)
this is part of my effort to modernise my soe-ci docs from "do this and that with hammer" to "run this or that playbook".
The text was updated successfully, but these errors were encountered: