Open johnkeates opened 7 years ago
Supplemental information:
On top of those, setting the user post-database creation (i.e. doing it manually first) also doesn't work. Something seems to be problematic with getting available users.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.
This is still a severe bug...
Thank you for updating this issue. It is no longer marked as stale.
Any update on this?
I have not seen or heard anything. Probably worth re-verifying this to be sure?
Hi @johnkeates , are you able to test this out on the latest version of salt?
I'm afraid we've switched away from SaltStack to something else for our database needs. I could probably get some really old commits from our Vagrant days and try it out, but I suppose that would only make sense if this specific issue was mitigated.
Description of Issue/Question
When postgres_database.present tries to create a database and assign it to a user, it always fails with a python exception and a stack trace.
Setup
Using postures-formula from saltstack-formulas at revision 5cbf920fa7f7d277a5dd874f08157f15aad3a19e
Pillar Data:
State:
Steps to Reproduce Issue
Running salt-call state.apply will do everything correctly except creating the database (and setting the user as the owner). The user is created fine. This issue has been happening since Debian 8 and Salt 2016.3.x
Postgres says:
This is done in a fresh vagrant box, and fails every time.
Versions Report