jnair75 opened a new issue, #29696:
URL: https://github.com/apache/airflow/issues/29696
### Apache Airflow version
Other Airflow 2 version (please specify below)
### What happened
Airflow 2.2.5
Running a DAG and got this error for a task.
[2023-02-22, 09:38:16 EST] {standard_task_runner.py:79} INFO - Running:
['airflow', 'tasks', 'run', 'icwg_fastqsr_ftp_service_volume',
'find_service_volume_for_fastqsr', 'manual__2023-02-22T14:38:11.752718+00:00',
'--job-id', '36461', '--raw', '--subdir',
'DAGS_FOLDER/icwg_fastqsr/icwg_fastqsr_ftp_service_volume.py', '--cfg-path',
'/tmp/tmp5lgl246c', '--error-file', '/tmp/tmpc2q98hw9']
[2023-02-22, 09:38:16 EST] {standard_task_runner.py:80} INFO - Job 36461:
Subtask find_service_volume_for_fastqsr
[2023-02-22, 09:38:17 EST] {task_command.py:298} INFO - Running
<TaskInstance: icwg_fastqsr_ftp_service_volume.find_service_volume_for_fastqsr
manual__2023-02-22T14:38:11.752718+00:00 [running]> on host airflow-worker-vtgg4
[2023-02-22, 09:38:17 EST] {taskinstance.py:1745} WARNING - We expected to
get frame set in local storage but it was not. Please report this as an issue
with full logs at https://github.com/apache/airflow/issues/new
Traceback (most recent call last):
### What you think should happen instead
No idea as the same DAG was running fine in another composer in same
project. We just copied this DAG from there and ran first time in order to
migrate the DAG to this composer.
### How to reproduce
Copy a DAG with Big Query operator from one composer to another running in
same project and start running it.
### Operating System
Ubuntu
### Versions of Apache Airflow Providers
Big Query Operator related
### Deployment
Google Cloud Composer
### Deployment details
Airflow on Google Cloud Composer 2.1.3
### Anything else
NA
### 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]