Attempting to Upgrade Chart to Enable Examples Causes Postgres Error #29444

Activity

1. victor-perchwell

   added

   area:helm-chartAirflow Helm ChartAirflow Helm Chart

   kind:bugThis is a clearly a bugThis is a clearly a bug

   on Feb 9, 2023
2. iuriqc commented on Feb 11, 2023

   

   iuriqc

   on Feb 11, 2023

   More actions

   I had a similar situation. When modifying the yaml to use gitsync and updating Airflow I had the same error. I tried modifying the "airflow-postgresql" secret to include the "password" key and the helm even completes the update, but postgres doesn't work properly. Following this orientation to delete the secret and statefulset also does not work.
3. hussein-awala commented on Feb 13, 2023

   

   hussein-awala

   on Feb 13, 2023

   Member

   More actions

   Is your current version deployed with 1.8.0 or earlier?
   If it's an earlier version, you need to update the values file, because we upgraded the postgresql chart from 10.5.3 to 12.1.9 and the schema of the values file (PR)
4. potiuk commented on Mar 2, 2023

   

   potiuk

   on Mar 2, 2023

   Member

   More actions

   Yes. This is a known "expectation" for chart 1.8.0 and the way how to deal with it is described in release notes
5. agentdanger commented on Mar 2, 2023

   

   agentdanger

   on Mar 2, 2023

   More actions

   I can recreate this issue by doing a fresh install using the 1.8 helm image "my-airflow", in a fresh namespace on kubernetes, and customizing the values.yaml to attempt to turn on git-sync. I have the same issue the original OP is mentioning.
6. agentdanger commented on Mar 2, 2023

   

   agentdanger

   on Mar 2, 2023

   More actions

   I get the issue when I do a helm upgrade to install the custom values.
7. agentdanger commented on Mar 2, 2023

   

   agentdanger

   on Mar 2, 2023

   Last edited by agentdanger

   More actions

   I was able to resolve this issue.

   Upgrading also refers to upgrading the existing 1.8.0 chart. You have to follow @potiuk suggestion within the release notes.

   kubectl delete secret {RELEASE_NAME}-postgresql
kubectl delete statefulset {RELEASE_NAME}-postgresql

   Then in your values.yaml file. You must set the username and password in the postgresql subchart configuration:

   postgresql:
   enabled: true
   image:
   tag: "11"
   auth:
   enablePostgresUser: true
   postgresPassword: postgres
   username: YOUR_USERNAME
   password: YOUR_PASSWORD

   No issues once I did all of those steps.
8. agentdanger commented on Mar 2, 2023

   

   agentdanger

   on Mar 2, 2023

   More actions

   I'm caveating my "no issue" suggestion above. I'm currently working through bugs on the git-sync but those could be my own doing. My work around was able to solve the postgresql error I was getting...
9. agentdanger commented on Mar 3, 2023

   

   agentdanger

   on Mar 3, 2023

   Last edited by agentdanger

   More actions

   I was able to solve this issue by installing 1.8 with the custom yaml file.

   My namespace for this implementation was colosseum.

   I had a custom yaml filed called values.yaml in the same working directory that I was performing my kubectl commands.
   I also had my git secret ready in the same working directory.

   kubectl commands I used are below:

   kubectl create namespace colosseum --dry-run=client -o yaml | kubectl apply -f -
kubectl create secret generic airflow-gke-git-secret --from-file=gitSshKey=airflow-gke-git-secret --namespace colosseum --dry-run=client -o yaml | kubectl apply -f -
helm upgrade --install my-airflow apache-airflow/airflow --namespace colosseum --create-namespace -f values.yaml --debug
10. potiuk commented on Mar 3, 2023

    

    potiuk

    on Mar 3, 2023

    Member

    More actions

    I am closing this one then as "no issue" - unless there are some new findings.
11. potiuk

    closed this as completedon Mar 3, 2023