santurini opened a new issue, #52969:
URL: https://github.com/apache/airflow/issues/52969
### Official Helm Chart version
1.17.0 (latest released)
### Apache Airflow version
2.9.2
### Kubernetes Version
1.31
### Helm Chart configuration
```
airflowHome: /opt/airflow
defaultAirflowRepository: apache/airflow
defaultAirflowTag: "2.9.2"
airflowVersion: "2.9.2"
images:
airflow:
repository: ${IMAGE_NAME}
tag: ${VERSION}
env:
- name: "AIRFLOW__API__AUTH_BACKEND"
value: "airflow.api.auth.backend.basic_auth"
- name: "AIRFLOW__CORE__DAGS_ARE_PAUSED_AT_CREATION"
value: "True"
- name: "AIRFLOW__CORE__LOAD_EXAMPLES"
value: "False"
- name: AIRFLOW__CORE__EXECUTE_TASKS_NEW_PYTHON_INTERPRETER
value: "True"
- name: AIRFLOW__LOGGING__REMOTE_LOGGING
value: "True"
- name: AIRFLOW__LOGGING__REMOTE_LOG_CONN_ID
value: "LoggingS3Connection"
- name: AIRFLOW__LOGGING__REMOTE_BASE_LOG_FOLDER
value: "s3://logs-archive-product-team/Airflow"
- name: AIRFLOW__LOGGING__ENCRYPT_S3_LOGS
value: "False"
- name: AIRFLOW__CORE__ENABLE_XCOM_PICKLING
value: "True"
- name: AIRFLOW__SMTP__SMTP_HOST
value: "smtp.gmail.com"
- name: AIRFLOW__SMTP__SMTP_PORT
value: "587"
- name: AIRFLOW__SMTP__SMTP_SSL
value: "False"
- name: AIRFLOW__SMTP__SMTP_STARTTLS
value: "True"
secret:
- envName: "GIT_TOKEN"
secretName: "airflow-git-token"
secretKey: "GIT_TOKEN"
- envName: "AWS_ACCESS_KEY_ID"
secretName: "airflow-aws"
secretKey: "AWS_ACCESS_KEY_ID"
- envName: "AWS_SECRET_ACCESS_KEY"
secretName: "airflow-aws"
secretKey: "AWS_SECRET_ACCESS_KEY"
- envName: "AWS_ACCESS_KEY_ID_DATASETS"
secretName: "airflow-aws"
secretKey: "AWS_ACCESS_KEY_ID_DATASETS"
- envName: "AWS_SECRET_ACCESS_KEY_DATASETS"
secretName: "airflow-aws"
secretKey: "AWS_SECRET_ACCESS_KEY_DATASETS"
- envName: "FRONT_TOKEN"
secretName: "airflow-connections"
secretKey: "FRONT_TOKEN"
- envName: "ASANA_TOKEN"
secretName: "airflow-connections"
secretKey: "ASANA_TOKEN"
- envName: "SLACK_TOKEN"
secretName: "airflow-connections"
secretKey: "SLACK_TOKEN"
- envName: "AIRFLOW__SMTP__SMTP_PASSWORD"
secretName: "airflow-connections"
secretKey: "AIRFLOW__SMTP__SMTP_PASSWORD"
- envName: "AWS_BUCKET_MODEL"
secretName: "airflow-aws"
secretKey: "AWS_BUCKET_MODEL"
- envName: "AWS_REGION_NAME"
secretName: "airflow-aws"
secretKey: "AWS_REGION_NAME"
- envName: "REDIS_PASSWORD"
secretName: "airflow-connections"
secretKey: "REDIS_PASSWORD"
- envName: "AIRFLOW_REDIS_URL"
secretName: "airflow-connections"
secretKey: "AIRFLOW_REDIS_URL"
data:
metadataConnection:
user: airflow
pass: ${AIRFLOW_DB_PASSWORD}
protocol: postgresql
host: postgres-prod.domain.com
port: 5432
db: airflow
sslmode: disable
brokerUrl: ${AIRFLOW_REDIS_URL}
fernetKey: ${FERNET_KEY}
dags:
gitSync:
enabled: true
repo: [email protected]:repo/airflow-dags.git
branch: master
ref: master
depth: 1
subPath: "dags"
sshKeySecret: airflow-ssh-secret
### Docker Image customizations
```
FROM apache/airflow:2.9.2-python3.11
ARG GIT_TOKEN
ENV GIT_TOKEN=$GIT_TOKEN
USER root
RUN apt-get update && apt-get install -y git
RUN apt-get install g++ -y
USER $AIRFLOW_UID
```
### What happened
I did an airflow fresh installation (new redis and postgre db) importing
variables and connections from a previous version, and now almost all the dags
fail with only these logs:
```
*** No logs found on s3 for ti=<TaskInstance:
enterprise_ops_quality_report_v2.get_variables
manual__2025-07-07T08:47:24.269460+00:00 [failed]>
*** Could not read served logs: Request URL is missing an 'http://'/ or
'https://'/ protocol.
```
I am no more able to make a succesfull DAG run, while before I had no
problems at all.
### What you think should happen instead
_No response_
### How to reproduce
Install airflow with provided helm values and try a DAG run.
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] 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]
