-
Notifications
You must be signed in to change notification settings - Fork 146
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
Pmm-init doesn't skip task with waiting for a local postgres even when an external postgres is used #3666
Comments
@ddkozyreva I believe this happens because you don't use the other set of variables that are necessary for Grafana to work correctly with an external database. As you can see, this part would not be executed if those If that is the case, I recommend you check out the relevant section in our docs. |
Are you talking about this condition
? This condition is for the block Postgres task has only one condition later - So if I need to upgrade pmm version and have an external postgres then I will face this postgres task and can't complete initialization process :( P.S. I have GF_DATABASE_URL env, so these tasks with grafana are skipped when i add the condition into the postgres task |
Pull Request for the problem #3667 |
Description
Hi!
We use an external postgres and define it with the PMM_POSTGRES_ADDR and PMM_DISABLE_BUILTIN_POSTGRES envs.
However the pmm-init process cannot work correctly due to the ansible task in the initialization role:
And the pmm-init cannot be completed correctly due to the failed task.
It would be great if you added a condition to the problem task like
when: lookup('env','PMM_POSTGRES_ADDR') == '127.0.0.1:5432' and lookup('env','PMM_DISABLE_BUILTIN_POSTGRES') != '1'
.Expected Results
We use an external postgres and expect the pmm-init process will work correctly.
Actual Results
The pmm-init runs the task for the local postgres and waits for task to be completed.
We don't have local postgres just because it runs on a separate host.
So the task fails and the playbook fails too.
Version
3.0.0
Steps to reproduce
No response
Relevant logs
Code of Conduct
The text was updated successfully, but these errors were encountered: