Startouf opened a new issue, #29530:
URL: https://github.com/apache/airflow/issues/29530

   ### Official Helm Chart version
   
   1.8.0 (latest released)
   
   ### Apache Airflow version
   
   2.5.1
   
   ### Kubernetes Version
   
   1.23.1 BuildDate:"2021-12-16T11:34:54Z"
   
   ### Helm Chart configuration
   
   Here is my values file. I also deployed airflow in a "dev" namespace with 
reckoner and generated weberver secrets with
   ```
   kubectl -n dev create secret generic airflow-webserver-secrets 
--from-literal="webserver-secret-key=$(python3 -c 'import secrets; 
print(secrets.token_hex(16))')"
   ```
   
   ```
   # airflow-values.yaml
   ingress:
     web:
       enabled: true
       annotations:
         cert-manager.io/cluster-issuer: letsencrypt-prod-http01
       hosts:
         - name: airflow.example.com
           tls:
             enabled: true
             secretName: airflow-tls-secret
     flower:
       enabled: false
       annotations:
         cert-manager.io/cluster-issuer: letsencrypt-prod-http01
       hosts:
         - name: airflow-flower.example.com
           tls:
             enabled: true
             secretName: airflow-flower-tls-secret
   webserverSecretKeySecretName: airflow-webserver-secrets
   
   # kubectl -n dev create secret generic airflow-webserver-secrets 
--from-literal="webserver-secret-key=$(python3 -c 'import secrets; 
print(secrets.token_hex(16))')"
   ```
   
   
   ### Docker Image customizations
   
   None
   
   ### What happened
   
   I deployed airflow to my kubernetes cluster on 3DS Outscale.
   The first deployment crashed the nodes (probably ran OOM because), so I 
rebooted the nodes and after waiting a bit all airflow related services seem to 
be up
   But when I connect to the web ingress, I have the "problem" screen, and when 
tailing the logs of the webserver I see this
   
   ```
       response = self.process_response(response)
     File "/home/airflow/.local/lib/python3.7/site-packages/flask/app.py", line 
2340, in process_response
       self.session_interface.save_session(self, ctx.session, response)
     File 
"/home/airflow/.local/lib/python3.7/site-packages/airflow/www/session.py", line 
33, in save_session
       return super().save_session(*args, **kwargs)
     File 
"/home/airflow/.local/lib/python3.7/site-packages/flask_session/sessions.py", 
line 580, in save_session
       session_id = self._get_signer(app).sign(want_bytes(session.sid))
   AttributeError: 'NoneType' object has no attribute 'sign'
   
   During handling of the above exception, another exception occurred:
   
   Traceback (most recent call last):
     File "/home/airflow/.local/lib/python3.7/site-packages/flask/app.py", line 
1844, in finalize_request
       response = self.process_response(response)
     File "/home/airflow/.local/lib/python3.7/site-packages/flask/app.py", line 
2340, in process_response
       self.session_interface.save_session(self, ctx.session, response)
     File 
"/home/airflow/.local/lib/python3.7/site-packages/airflow/www/session.py", line 
33, in save_session
       return super().save_session(*args, **kwargs)
     File 
"/home/airflow/.local/lib/python3.7/site-packages/flask_session/sessions.py", 
line 580, in save_session
       session_id = self._get_signer(app).sign(want_bytes(session.sid))
   AttributeError: 'NoneType' object has no attribute 'sign'
   ```
   
   Note that healthchecks are reported as successful
   
   10.233.64.1 - - [14/Feb/2023:11:27:46 +0000] "GET /health HTTP/1.1" 200 141 
"-" "kube-probe/1.23"
   
   ### What you think should happen instead
   
   I should reach the login or first setup interface ?
   
   ### How to reproduce
   
   Simply by installing the chart. Maybe when the node crashed on initial 
deploy, some migrations/one-time run scripts did not run successfully and 
caused irreversible problems ?
   
   ### Anything else
   
   I edited some values and made a second release (to add the 
webserverSecretKeySecretName since I saw a warning in the INFOs) and 
successfully deployed a new version. The output of my info file is
   
   ```
   Release "airflow" has been upgraded. Happy Helming!
   NAME: airflow
   LAST DEPLOYED: Tue Feb 14 11:59:29 2023
   NAMESPACE: dev
   STATUS: deployed
   REVISION: 2
   TEST SUITE: None
   NOTES:
   Thank you for installing Apache Airflow 2.5.1!
   
   Your release is named airflow.
   You can now access your service(s) by following defined Ingress urls:
   
   DEPRECATION WARNING:
      `ingress.web.tls` has been renamed to `ingress.web.hosts[*].tls` and can 
be set per host.
      Please change your values as support for the old name will be dropped in 
a future release.
   
   DEPRECATION WARNING:
      `ingress.flower.tls` has been renamed to `ingress.flower.hosts[*].tls` 
and can be set per host.
      Please change your values as support for the old name will be dropped in 
a future release.
   Airflow Webserver:
         https://airflow.example.com//
   Default Webserver (Airflow UI) Login credentials:
       username: admin
       password: admin
   Default Postgres connection credentials:
       username: postgres
       password: postgres
       port: 5432
   
   You can get Fernet Key value by running the following:
   
       echo Fernet Key: $(kubectl get secret --namespace dev airflow-fernet-key 
-o jsonpath="{.data.fernet-key}" | base64 --decode)
   
   ```
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to