pankajkoti opened a new issue, #64632: URL: https://github.com/apache/airflow/issues/64632
### Apache Airflow version 3.2.0rc1 ### What happened and how to reproduce it? I am testing 3.2.0rc1 and seeing issues in DAGs using remote `ObjectStoragePath` (tried S3 and GCS paths) . The same DAG works fine on 3.1.8. For both these airflow versions, I am using the latest amazon and google providers, so likely not a provider issue, but maybe something related to airflow / sdk not being able to fetch credentials? I am setting up those connections using environment variables for my local environment. ### What you think should happen instead? DAGs should run fine when using remote `ObjectStoragePath` ### Operating System _No response_ ### Versions of Apache Airflow Providers apache-airflow-providers-amazon | 9.24.0 apache-airflow-providers-google | 21.0.0 ### Deployment Astronomer ### Deployment details locally using astro-cli ### Anything else? Attaching failure task logs: GCS ObjectStoragePath task: [logs_test_object_storage_path_manual__2026-04-02T14_43_24.115545+00_00_check_gcs_-1_1.txt](https://github.com/user-attachments/files/26441753/logs_test_object_storage_path_manual__2026-04-02T14_43_24.115545%2B00_00_check_gcs_-1_1.txt) S3 ObjectStoragePath task: [logs_test_object_storage_path_manual__2026-04-02T14_43_24.115545+00_00_check_s3_-1_1.txt](https://github.com/user-attachments/files/26441754/logs_test_object_storage_path_manual__2026-04-02T14_43_24.115545%2B00_00_check_s3_-1_1.txt) DAG: [test_object_storage_path.py](https://github.com/user-attachments/files/26441762/test_object_storage_path.py) ### 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]
