joaofelipecb opened a new issue, #19909:
URL: https://github.com/apache/superset/issues/19909

   When I tried to run helm chart v0.6.0, I notice that the db init job could 
not run. Also, I looked for logs of the postgres pod and I catched a 
authentication error.
   
   ```
   2022-04-30 12:15:37.534 GMT [195] FATAL:  password authentication failed for 
user "superset"
   2022-04-30 12:15:37.534 GMT [195] DETAIL:  Role "superset" does not exist.
           Connection matched pg_hba.conf line 1: "host     all
   all             0.0.0.0/0               md5"
   ```
   
   #### How to reproduce the bug
   
   ```
   helm repo add superset https://apache.github.io/superset
   helm upgrade --install --create-namespace --namespace superset superset 
superset/superset --version 0.6.0
   kubectl get -n superset pod -w
   ```
   
   Output:
   
   ```
   NAME                              READY   STATUS             RESTARTS   AGE
   superset-6d99875f75-wvvnr         1/1     Running            0          9m28s
   superset-init-db-8smqz            0/1     Error              0          22s
   superset-init-db-gd8wb            0/1     Error              0          39s
   superset-init-db-xfchk            0/1     Error              0          32s
   superset-postgresql-0             1/1     Running            0          9m28s
   superset-redis-master-0           1/1     Running            0          9m28s
   superset-worker-bb4d67447-ljbth   0/1     CrashLoopBackOff   6          9m28s
   ```
   
   `kubectl logs superset-postgresql-0 -n superset`
   
   Output:
   
   ```
   2022-04-30 12:15:37.534 GMT [195] FATAL:  password authentication failed for 
user "superset"
   2022-04-30 12:15:37.534 GMT [195] DETAIL:  Role "superset" does not exist.
           Connection matched pg_hba.conf line 1: "host     all
   all             0.0.0.0/0               md5"
   ```
   
   ### Expected results
   
   The database inicialization performs correctly via helm instalation.
   
   ### Actual results
   
   The database inicialization doesn't perform correctly via helm instalation 
because of authentication error when try to connect to the postgresql database.
   
   #### Screenshots
   
   If applicable, add screenshots to help explain your problem.
   
   
   ### Environment
   
   (please complete the following information):
   
   - browser type and version: N/A
   - superset version: helm chart 0.6.0
   - python version: Python 3.8.10
   - node.js version: N/A
   - any feature flags active:
   - kubernetes version: Client Version: version.Info{Major:"1", Minor:"22", 
GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", 
GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", 
Compiler:"gc", Platform:"windows/amd64"}
   Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.5", 
GitCommit:"aea7bbadd2fc0cd689de94a54e5b7b758869d691", GitTreeState:"clean", 
BuildDate:"2021-09-15T21:04:16Z", GoVersion:"go1.16.8", Compiler:"gc", 
Platform:"linux/amd64"}
   - Helm Version: version.BuildInfo{Version:"v3.8.2", 
GitCommit:"6e3701edea09e5d55a8ca2aae03a68917630e91b", GitTreeState:"clean", 
GoVersion:"go1.17.5"}
   
   ### Checklist
   
   Make sure to follow these steps before submitting your issue - thank you!
   
   - [ ] I have checked the superset logs for python stacktraces and included 
it here as text if there are any.
   - [ ] I have reproduced the issue with at least the latest released version 
of superset.
   - [ ] I have checked the issue tracker for the same issue and I haven't 
found one similar.
   
   ### Additional context
   
   I notice that the helm chart was recently updated. In chart version 5.11.0 
it works correctly.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to