-
Notifications
You must be signed in to change notification settings - Fork 96
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
Database ping test fails when the username and dbname is different in initdb #368
Labels
chart( cluster )
Related to the cluster chart
Comments
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Aug 30, 2024
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Aug 30, 2024
Signed-off-by: Uğurcan Akkök <[email protected]>
UgurcanAkkok
changed the title
Helm test hook fails when the username and dbname is different in initdb
Database ping test fails when the username and dbname is different in initdb
Aug 30, 2024
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Sep 6, 2024
Signed-off-by: Uğurcan Akkök <[email protected]>
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Sep 9, 2024
Signed-off-by: Uğurcan Akkök <[email protected]>
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Sep 9, 2024
Signed-off-by: Uğurcan Akkök <[email protected]>
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Nov 6, 2024
Signed-off-by: Uğurcan Akkök <[email protected]>
UgurcanAkkok
added a commit
to UgurcanAkkok/cloudnative-pg-charts
that referenced
this issue
Nov 6, 2024
Signed-off-by: Uğurcan Akkök <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi everyone,
The database-ping-test fails when i set the value of the database different from the owner in the initdb configuration.
Following is my configuration for cluster chart, I am using kustomize to deploy helm
And this results in the following error in the ping-test pod:
As you can see it tries to connect to
gitea
database, even though we specified it asgiteadb
The connection string and pod configuration:
When I manually try to connect with the giteadb, i can succesfully create a connection:
So the problem is, in the test-pod there is no db specified so it (by default) tries to connect to a db with the same name as the user. As there is no db created as such, it fails.
The text was updated successfully, but these errors were encountered: