kundan1301 opened a new issue #10087:
URL: https://github.com/apache/airflow/issues/10087


   <!--
   
   Welcome to Apache Airflow!  For a smooth issue process, try to answer the 
following questions.
   Don't worry if they're not all applicable; just try to include what you can 
:-)
   
   If you need to include code snippets or logs, please put them in fenced code
   blocks.  If they're super-long, please use the details tag like
   <details><summary>super-long log</summary> lots of stuff </details>
   
   Please delete these comment blocks before submitting the issue.
   
   -->
   
   <!--
   
   IMPORTANT!!!
   
   PLEASE CHECK "SIMILAR TO X EXISTING ISSUES" OPTION IF VISIBLE
   NEXT TO "SUBMIT NEW ISSUE" BUTTON!!!
   
   PLEASE CHECK IF THIS ISSUE HAS BEEN REPORTED PREVIOUSLY USING SEARCH!!!
   
   Please complete the next sections or the issue will be closed.
   This questions are the first thing we need to know to understand the context.
   
   -->
   
   **Apache Airflow version**: 1.10.9
   
   
   **Kubernetes version (if you are using kubernetes)** (use `kubectl version`):
   
   **Environment**: composer
   
   - **Cloud provider or hardware configuration**: google
   - **OS** (e.g. from /etc/os-release):
   - **Kernel** (e.g. `uname -a`):
   - **Install tools**:
   - **Others**:
   
   **What happened**: AWSHook throwing TypeError: 'NoneType' object is not 
callable
   
   <!-- (please include exact error messages if you can) -->
   
   **What you expected to happen**:
   It should throw actual error. 
   
   **What do you think went wrong? **: 
   
   Catching exception but not logging exception. 
   
https://github.com/apache/airflow/blob/1.10.9/airflow/contrib/operators/gcp_transfer_operator.py#L55
   At this line AWSHook is set to None, before setting that we should log 
exception. Cloud composer don't install boto3 by default, because of this an 
exception is thrown  which causes AWSHook set to None.  Which in turn throwing 
error at line 
   
https://github.com/apache/airflow/blob/1.10.9/airflow/contrib/operators/gcp_transfer_operator.py#L71
   
   
   stacktrace
   
   Traceback (most recent call last)
     File "/usr/local/lib/airflow/airflow/models/taskinstance.py", line 972, in 
_run_raw_tas
       result = task_copy.execute(context=context
     File 
"/usr/local/lib/airflow/airflow/contrib/operators/gcp_transfer_operator.py", 
line 638, in execut
       TransferJobPreprocessor(body=body, aws_conn_id=self.aws_conn_id, 
default_schedule=True).process_body(
     File 
"/usr/local/lib/airflow/airflow/contrib/operators/gcp_transfer_operator.py", 
line 108, in process_bod
       self._inject_aws_credentials(
     File 
"/usr/local/lib/airflow/airflow/contrib/operators/gcp_transfer_operator.py", 
line 71, in _inject_aws_credential
       aws_hook = AwsHook(self.aws_conn_id)
   
   
    
   
   **How to reproduce it**:
   <!---
   
   As minimally and precisely as possible. Keep in mind we do not have access 
to your cluster or dags.
   
   If you are using kubernetes, please attempt to recreate the issue using 
minikube or kind.
   
   ## Install minikube/kind
   
   - Minikube https://minikube.sigs.k8s.io/docs/start/
   - Kind https://kind.sigs.k8s.io/docs/user/quick-start/
   
   If this is a UI bug, please provide a screenshot of the bug or a link to a 
youtube video of the bug in action
   
   You can include images using the .md sytle of
   ![alt text](http://url/to/img.png)
   
   To record a screencast, mac users can use QuickTime and then create an 
unlisted youtube video with the resulting .mov file.
   
   --->
   
   
   **Anything else we need to know**:
   
   <!--
   
   How often does this problem occur? Once? Every time etc?
   
   Any relevant logs to include? Put them here in side a detail tag:
   <details><summary>x.log</summary> lots of stuff </details>
   
   -->
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to