jain6968 opened a new issue #12943: URL: https://github.com/apache/airflow/issues/12943
<!-- 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. These questions are the first thing we need to know to understand the context. --> **Apache Airflow version**: composer-1.11.2-airflow-1.10.6 **Kubernetes version (if you are using kubernetes)** (use `kubectl version`): 1.16.13 apiVersion: kubelet.config.k8s.io/v1beta1 **Environment**: Using compute engine 1) composer-1.11.2-airflow-1.10.6 2) Python – 3.6 3) 'dbt==0.17.0', 4) 'google-cloud-storage', 5) 'google-cloud-secret-manager==1.0.0', 6) 'protobuf==3.12.2' - **Cloud provider or hardware configuration**: gcp compute engine - **OS** (e.g. from /etc/os-release): Debian , Intel Broadwell - **Kernel** (e.g. `uname -a`): n1-standard-1 (1 vCPU, 3.75 GB memory) - **Install tools**: python sdk 3.6.0 - **Others**: apache beam , dbt **What happened**: Below is the configuration which worked till December 1st 1) composer-1.11.2-airflow-1.10.6 2) Python – 3.6 3) 'dbt==0.17.0', 4) 'google-cloud-storage', 5) 'google-cloud-secret-manager==1.0.0', 6) 'protobuf==3.12.2' With the above configuration we are observing below error. ERROR: Cannot install dbt and protobuf==3.12.2 because these package versions have conflicting dependencies.\n\nThe conflict is caused by:\n The user requested protobuf==3.12.2\n dbt-bigquery 0.17.0 depends on protobuf<3.12 and >=3.6.0\n\nTo fix this you could try to:\n1. loosen the range of package versions you've specified\n2. remove package versions to allow pip attempt to solve the dependency conflict\n\nERROR: ResolutionImpossible Post receiving this error message we have tried many version changes to resolve the above issue. Below listed are few of the fixes applied and errors we have observed for those fixes. 1) Fix applied: downgraded protobuf version from 3.12.2 to 3.11.3 as per the above error Error: Requested docutils<0.16,>=0.10 from https://files.pythonhosted.org/packages/d4/12/6c3fd74a590c7327c98cae008c11d536029fa9cd7924de477e8cb8804186/docutils-0.15.1-post1.tar.gz#sha256=f33ddb723332c6d6b6d99731ee1fc0c35eb4044a2df5cca1c64c8aa78eaf22cb (from botocore<1.15,>=1.5.0->dbt-redshift==0.17.0->dbt==0.17.0) has different version in metadata: '0.15.1' 2) Fix applied: Specified docutils version to 0.15.2 as to fix the above error Error: SyntaxError: Missing parentheses in call to \'print\'. Did you mean print("Generating %s..." % output)?\n ----------------------------------------\nERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. 3) Fix applied: Tried upgrading python version from 3.6 to 3.8. Error: The path python3.8 (from --python=python3.8) does not exist. 4) Fix applied: Removed package versioning for above libraries to allow pip attempt to solve the dependency conflict. Error: Command errored out with exit status 1:\n command: /tmp/venv__vuo821/bin/python3.6 -c \'import sys, setuptools, tokenize; sys.argv[0] = \'"\'"\'/tmp/pip-install-ghz6thkq/protobuf_a5303ec5c2df4986bb9b05948ae30052/setup.py\'"\'"\'; __file__=\'"\'"\'/tmp/pip-install-ghz6thkq/protobuf_a5303ec5c2df4986bb9b05948ae30052/setup.py\'"\'"\';f=getattr(tokenize, \'"\'"\'open\'"\'"\', open)(__file__);code=f.read().replace(\'"\'"\'\\r\\n\'"\'"\', \'"\'"\'\\n\'"\'"\');f.close();exec(compile(code, __file__, \'"\'"\'exec\'"\'"\'))\' egg_info --egg-base /tmp/pip-pip-egg-info-gi38587q\n cwd: /tmp/pip-install-ghz6thkq/protobuf_a5303ec5c2df4986bb9b05948ae30052/\n Complete output (6 lines):\n Traceback (most recent call last):\n File "<string>", line 1, in <module>\n File "/tmp/pip-install-ghz6thkq/protobuf_a5303ec5c2df4986bb9b05948ae30052/setup.py", line 52\n print "Generating %s..." % output\n ^\n SyntaxError: Missing parenthes es in call to \'print\'. Did you mean print("Generating %s..." % output)?\n ----------------------------------------\nERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output 5) Fix applied: Upgraded dbt to 0.17.2 Error: Received SIGTERM. Terminating subprocesses. 6) Fix applied: Tried downgrading setuptools version to 49.6.0 Error: SyntaxError: Missing parentheses in call to \'print\'. Did you mean print("Generating %s..." % output)?\n ------------------------------- ---------\nERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. 7) Fix applied: upgraded Composer and Airflow versions to composer-1.13.2-airflow-1.10.9 Error: Got similar errors with above configuration combinations **What you expected to happen**: We expect the DAG to complete and run the python script without any dependency issues. **How to reproduce it**: with Airflow version composer-1.11.2-airflow-1.10.6 and environment configs. **Error Details from logs**: ERROR: Cannot install dbt and protobuf==3.12.2 because these package versions have conflicting dependencies.\n\nThe conflict is caused by:\n The user requested protobuf==3.12.2\n dbt-bigquery 0.17.0 depends on protobuf<3.12 and >=3.6.0\n\nTo fix this you could try to:\n1. loosen the range of package versions you've specified\n2. remove package versions to allow pip attempt to solve the dependency conflict\n\nERROR: ResolutionImpossible" **Anything else we need to know**: Apart from the above fixes we have tried other combinations of packages and specifying package versions mentioned in https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies Unfortunately none of those fixes worked. <!-- How often does this problem occur? Once? Every time etc? Yes, everytime the DAG run with this configs. ---------------------------------------------------------------- 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]
