-
Notifications
You must be signed in to change notification settings - Fork 93
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
postgresql_privs fails with type=default_privs, privs=ALL, objs=ALL_DEFAULT #373
Comments
Github is not cooperating with me. I was still writing when I accidentally posted the issue. I'll have another look before I maybe open the issue again. |
OK, now I think I have a proper issue. Sorry about the editing mess. |
thanks for the report @vonschultz ! did you want to look into this @Andersson007 ? |
@vonschultz @vonschultz hi, yes, thanks, when I feel better, I'll take a look @vonschultz could you please run your tasks with |
This is the output of the task when running with
There's no traceback in the Python sense, just a sequence of shell commands and the failure. |
@vonschultz thanks! Could you folks please take a look? |
@vonschultz thanks for the issue! The investigation really helped much. |
I can confirm that version 2.3.1 installed through |
@vonschultz great, thanks for the feedback! |
SUMMARY
With Ansible 6.6.0
postgresql_privs
fails when running with type=default_privs, privs=ALL, objs=ALL_DEFAULT. The issue appears to have been introduced in commit eed4e1f which addedSCHEMAS
to theVALID_DEFAULT_OBJS
variable and thereby to theALL_DEFAULT
objs, despiteSCHEMAS
not being supported withprivs=ALL
.ISSUE TYPE
COMPONENT NAME
postgresql_privs
ANSIBLE VERSION
Note that the problem is not exhibited in
ansible
version 6.5.0.COLLECTION VERSION
CONFIGURATION
ansible-config dump --only-changed
reports no changesOS / ENVIRONMENT
Ubuntu 20.04, Postgresql 13.
STEPS TO REPRODUCE
This is the exact task that's failing for me with
ansible
version 6.6.0, but which works fine foransible
version 6.5.0:I think you'll find that this example in the documentation exhibits the same problem:
EXPECTED RESULTS
Task runs without error on latest version of
ansible
(given that it runs without error onansible
6.5.0).ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: