Skip to content

Incorrect timezone display in task log view #52056

Open
@humit0

Description

@humit0

Apache Airflow version

3.0.2

If "Other Airflow 2 version" selected, which one?

No response

What happened?

The time field in the task logs displayed on the web interface is showing an incorrect timezone.

Although the default timezone is configured to KST (+09:00) and the web display is also set to KST, the times are being displayed in UTC. And log files are also recording in UTC.

web

Image

log file
Image

What you think should happen instead?

How to reproduce

Configured environment variables

export AIRFLOW_HOME=/tmp/airflow
export AIRFLOW__CORE__LOAD_EXAMPLES=False
export AIRFLOW__CORE__DEFAULT_TIMEZONE=Asia/Seoul

DAG

from airflow.models import DAG
from airflow.providers.standard.operators.bash import BashOperator

default_args = {
    "owner": "airflow",
    "depends_on_past": False,
    "start_date": "2023-01-01",
    "retries": 1,
}

with DAG(
    dag_id="test_dag",
    default_args=default_args,
    schedule="@once",
) as dag:
    BashOperator(
        task_id="test_task",
        bash_command="echo '{{ ds }}'",
    )

Operating System

MacOS

Versions of Apache Airflow Providers

apache-airflow-providers-amazon==9.8.0
apache-airflow-providers-apache-spark==5.3.0
apache-airflow-providers-celery==3.11.0
apache-airflow-providers-common-compat==1.7.0
apache-airflow-providers-common-io==1.6.0
apache-airflow-providers-common-sql==1.27.1
apache-airflow-providers-http==5.3.0
apache-airflow-providers-postgres==6.2.0
apache-airflow-providers-redis==4.1.0
apache-airflow-providers-smtp==2.1.0
apache-airflow-providers-standard==1.2.0

Deployment

Virtualenv installation

Deployment details

Running with airflow standalone command

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

Labels

area:UIRelated to UI/UX. For Frontend Developers.area:corearea:loggingkind:bugThis is a clearly a bugpriority:mediumBug that should be fixed before next release but would not block a release

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions