-
Notifications
You must be signed in to change notification settings - Fork 107
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
[BUG] Not possible to debug failures in applications role #1792
Comments
mkyc
added
priority/high
Task with high priority
and removed
priority/important-soon
labels
Oct 23, 2020
Tested scenario:
Output:
Additionally the presence and contents of the file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There is no right error message on K8s deployment failure.
Example scenario:
block
andrescue
section generates erlang cookie.Deployment of RabbitMQ, Ignite, Auth Service and Pgpool succeeded.
Deployment of PgBouncer failed.
The reason of failure is hidden:
fatal: [127.0.0.1]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
.The mentioned debug file does not exists:
/shared/build/devhaazurubucanal/vault//applications/pgbouncer/debug.yml
.The error message is incorrect. It's related to rabbitmq-cluster-cookie task, not to the failed (PgBouncer) task.
Expected behavior
Show the right error message and debug file available.
Config files
Standard with enabled applications.
Second example
Additional context
n/a
The text was updated successfully, but these errors were encountered: