nlarge-google opened a new issue, #40945:
URL: https://github.com/apache/airflow/issues/40945

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   Unknown, but definitely version 2.x.x
   
   ### What happened?
   
   Last week Dags began erroring with ""Repeated values for field 
enableComponents may not be None"" when they had been working fine prior.  I 
have no idea why all of a sudden this issue occurred and have checked whether 
enableComponents is set in LoggingConfig and monitoringConfig - which they are. 
 Why then would a GKEStartPodOperator begin erroring with this, without any 
changes to the actual pods?
   
   ### What you think should happen instead?
   
   These pods worked last week with no changes and all of a sudden they do not.
   
   ### How to reproduce
   
   * In the pipline.yaml file, instantiate a GKECreateClusterOperator * 
following this instantiate a GKEStartPodOperator * run these in the dag.  * 
Fails with "Repeated values for field enableComponents may not be None"
   
   ### Operating System
   
   linux
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-common-sql==1.3.0
   apache-airflow-providers-ftp==3.1.0
   apache-airflow-providers-google==8.5.0
   apache-airflow-providers-http==4.0.0
   apache-airflow-providers-imap==3.0.0
   apache-airflow-providers-sendgrid==3.0.0
   apache-airflow-providers-sqlite==3.2.1
   
   
   ### Deployment
   
   Google Cloud Composer
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   It just started last week without any changes to any dags and the issue has 
occurred on multiple dags
   
   ### 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]

Reply via email to