You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit update the vip-manager version (use API v3) changes checking from 22 port to 5432 port.
But if we check patroni.yml we see that 5432 port is accessible only when pgbouncer doesn't used.
If we set pgbouncer_install=true then port 5432 doen't accessible by vip address and task is failed.
Resolve1: return back checking from 5432 to 22 port for task "Wait for the cluster ip address (VIP) "{{ cluster_vip }}" is running"
Resolve2: listen 5432 port on vip address no matter of using pgbouncer - change patroni.yml
If you prefer I can create pull request for one of resolution.
The text was updated successfully, but these errors were encountered:
This commit update the vip-manager version (use API v3) changes checking from 22 port to 5432 port.
But if we check patroni.yml we see that 5432 port is accessible only when pgbouncer doesn't used.
If we set pgbouncer_install=true then port 5432 doen't accessible by vip address and task is failed.
Resolve1: return back checking from 5432 to 22 port for task "Wait for the cluster ip address (VIP) "{{ cluster_vip }}" is running"
Resolve2: listen 5432 port on vip address no matter of using pgbouncer - change patroni.yml
If you prefer I can create pull request for one of resolution.
The text was updated successfully, but these errors were encountered: