-
Notifications
You must be signed in to change notification settings - Fork 574
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
UnableToCreateStanzas warning with wrong address for backup repo pod #3907
Comments
Hi @burigolucas! This error appears to be due to a network issue within your Kubernetes cluster. More specifically, the address for accessing the pgBackRest repo host Service per the logs and I therefore suggest checking out the Kubernetes docs for troubleshooting DNS to get the bottom of the network issue within your env: https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ This does not appear to be an issue with CPK itself, since CPK is forming the proper DNS name for the Service per the DNS for Services and Pod docs. Hope this helps! |
Overview
By creating a postgres cluster, a warning event with reason UnableToCreateStanzas is created with following message:
command terminated with exit code 49: ERROR: [049]: unable to get address for 'db1-repo-host-0.db1-pods.demo-database.svc.kubernetes.default.': [-2] Name or service not known
The cronjob for the backup is not created resulting in the WAL filling up the disk of the postgres instance.
Environment
Please provide the following details:
Steps to Reproduce
REPRO
Provide steps to get to the error condition:
Sample of postgres cluster definition:
EXPECTED
cronjob for backup to be created and backups to local repo1 to happen as per schedule.
ACTUAL
Please, see below logs of the operator:
Logs
Additional information
Please, see below the description of the postgres cluster:
The text was updated successfully, but these errors were encountered: