skymalorid commented on issue #10028:
URL: https://github.com/apache/airflow/issues/10028#issuecomment-1485336507
Apache Airflow version:
`airflow-2.2.5`
Composer version:
`composer-2.0.13`
Kubernetes version:
`1.24.9-gke.3200`
OS:
`Windows 11 Enterprise 22H2`
Cloud provider:
`GCP`
Install tools:
`Google Cloud SDK 418.0.0`
`beta 2023.02.13`
`bq 2.0.85`
`core 2023.02.13`
`gsutil 5.20`
`kubectl 1.24.10`
What happened:
If I issue the command,
```
gcloud composer environments run ${composer-name} --project ${project-name}
--location ${location} dags backfill -- --reset-dagruns -y -s ${date-start} -e
${date -end} --verbose -i -t ${task-name} ${dag-name} --dry-run
```
as indicated in the documentation:
https://cloud.google.com/composer/docs/how-to/accessing/airflow-cli#running-commands
https://airflow.apache.org/docs/apache-airflow/stable/cli-and-env-variables-ref.html#backfill
Everything works correctly, the indo of the dry-run are exactly those
expected,
But once the dry-run has been removed, the command is executed by Airflow,
but only the INFO message returns in the terminal
```
[2023-03-27 15:14:07,137] {backfill_job.py:789} INFO - No run dates were
found for the given dates and dag interval.
```
What did you expect to happen:
That it returned the information of the dag launched and executed by Airflow
How to play it:
Using Airflow/composer on GCP with the indicated versions and using the
Gcloud cli version by running the backfill on a specific task.
There is something else we need to know:
After contacting google it would appear to be a lib Airflow issue
--
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]
