Skip to content
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

Task "vip-manager : Wait for the cluster ip address (VIP)" is failed when is used pgbouncer #286

Closed
FactorT opened this issue Mar 22, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@FactorT
Copy link
Contributor

FactorT commented Mar 22, 2023

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.

@vitabaks
Copy link
Owner

Exactly you are right. Thanks!

it is necessary to return the "{{ ansible_ssh_port | default(22) }}"

vitabaks added a commit that referenced this issue Mar 22, 2023
@vitabaks vitabaks self-assigned this Mar 22, 2023
@vitabaks
Copy link
Owner

fixed: e4a7524

@vitabaks vitabaks added the bug Something isn't working label Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants