[ 
https://issues.apache.org/jira/browse/AIRFLOW-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797235#comment-16797235
 ] 

ASF subversion and git services commented on AIRFLOW-3758:
----------------------------------------------------------

Commit 753cc45730d4afe7a0f15e3fc1d59d3c0d06d1d2 in airflow's branch 
refs/heads/v1-10-stable from Tanay Tummalapalli
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=753cc45 ]

[AIRFLOW-3758] Fix circular import in WasbTaskHandler (#4601)

WasbHook was causing a circular import error when configure_logging() was 
called.

> Airflow command fails when remote logging enabled to azure blob
> ---------------------------------------------------------------
>
>                 Key: AIRFLOW-3758
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3758
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 1.10.2
>            Reporter: Marko Kattelus
>            Assignee: Tanay Tummalapalli
>            Priority: Major
>             Fix For: 1.10.3
>
>
> I tried to update to 1.10.2 but when running
> {code:java}
> airflow initdb
> {code}
> I get following:
> {code:java}
> webserver_1 | Updating database
> webserver_1 | Unable to load the config, contains a configuration error.
> webserver_1 | Traceback (most recent call last):
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 390, in 
> resolve
> webserver_1 | found = getattr(found, frag)
> webserver_1 | AttributeError: module 'airflow.utils.log' has no attribute 
> 'wasb_task_handler'
> webserver_1 |
> webserver_1 | During handling of the above exception, another exception 
> occurred:
> webserver_1 |
> webserver_1 | Traceback (most recent call last):
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 392, in 
> resolve
> webserver_1 | self.importer(used)
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/utils/log/wasb_task_handler.py",
>  line 23, in <module>
> webserver_1 | from airflow.contrib.hooks.wasb_hook import WasbHook
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/contrib/hooks/wasb_hook.py", 
> line 22, in <module>
> webserver_1 | from airflow.hooks.base_hook import BaseHook
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/hooks/base_hook.py", line 28, 
> in <module>
> webserver_1 | from airflow.models import Connection
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/models.py", line 86, in 
> <module>
> webserver_1 | from airflow.utils.dag_processing import list_py_file_paths
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/utils/dag_processing.py", 
> line 49, in <module>
> webserver_1 | from airflow.settings import logging_class_path
> webserver_1 | ImportError: cannot import name 'logging_class_path'
> webserver_1 |
> webserver_1 | The above exception was the direct cause of the following 
> exception:
> webserver_1 |
> webserver_1 | Traceback (most recent call last):
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 565, in 
> configure
> webserver_1 | handler = self.configure_handler(handlers[name])
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 715, in 
> configure_handler
> webserver_1 | klass = self.resolve(cname)
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 399, in 
> resolve
> webserver_1 | raise v
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 392, in 
> resolve
> webserver_1 | self.importer(used)
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/utils/log/wasb_task_handler.py",
>  line 23, in <module>
> webserver_1 | from airflow.contrib.hooks.wasb_hook import WasbHook
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/contrib/hooks/wasb_hook.py", 
> line 22, in <module>
> webserver_1 | from airflow.hooks.base_hook import BaseHook
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/hooks/base_hook.py", line 28, 
> in <module>
> webserver_1 | from airflow.models import Connection
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/models.py", line 86, in 
> <module>
> webserver_1 | from airflow.utils.dag_processing import list_py_file_paths
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/utils/dag_processing.py", 
> line 49, in <module>
> webserver_1 | from airflow.settings import logging_class_path
> webserver_1 | ValueError: Cannot resolve 
> 'airflow.utils.log.wasb_task_handler.WasbTaskHandler': cannot import name 
> 'logging_class_path'
> webserver_1 |
> webserver_1 | During handling of the above exception, another exception 
> occurred:
> webserver_1 |
> webserver_1 | Traceback (most recent call last):
> webserver_1 | File "/usr/local/bin/airflow", line 21, in <module>
> webserver_1 | from airflow import configuration
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/__init__.py", line 36, in 
> <module>
> webserver_1 | from airflow import settings, configuration as conf
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/settings.py", line 262, in 
> <module>
> webserver_1 | logging_class_path = configure_logging()
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/logging_config.py", line 72, 
> in configure_logging
> webserver_1 | raise e
> webserver_1 | File 
> "/usr/local/lib/python3.6/site-packages/airflow/logging_config.py", line 67, 
> in configure_logging
> webserver_1 | dictConfig(logging_config)
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 802, in 
> dictConfig
> webserver_1 | dictConfigClass(config).configure()
> webserver_1 | File "/usr/local/lib/python3.6/logging/config.py", line 573, in 
> configure
> webserver_1 | '%r: %s' % (name, e))
> webserver_1 | ValueError: Unable to configure handler 'processor': Cannot 
> resolve 'airflow.utils.log.wasb_task_handler.WasbTaskHandler': cannot import 
> name 'logging_class_path'
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to