-
Notifications
You must be signed in to change notification settings - Fork 573
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
cluster_reset has no effect on Debian #253
Labels
Comments
are you still having this issue? |
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
On Ubuntu, my test case is:
I then in vars.yml added
postgresql_cluster_reset: true
(since the default is false)Looking at configure.yml I see for the drop and create cluster tasks the following condition:
when: ansible_os_family == "Debian" and postgresql_cluster_reset and pgdata_dir_exist.changed
However, pgdata_dir_exists only changes when the data dir is dropped, which is limited to RedHat.
From my understanding pg_dropcluster + pg_createcluster is all that is needed in Ubuntu, as seems to be the configure.yml's intention, except for the limit; I reasoned I could solve the problem if for all the Debian steps I just remove that condition:
when: ansible_os_family == "Debian" and postgresql_cluster_reset
This results in this error:
unable to connect to database: FATAL: could not open relation mapping file "global/pg_filenode.map
Every second run fails, every run in between succeeds. (success, fail, success, fail..)
Am I getting this wrong, or is this a bug?
The text was updated successfully, but these errors were encountered: