IssueTracker

Hello,

Thank you for reaching out.

The Product team is working on this issue. This request has no ETA, but you can follow the progress in this thread.

Workaround for Fedora 35: Downgrade python 3 or add the following to .bashrc:

export CLOUDSDK_PYTHON=/usr/bin/python2

The fix is released with gcloud version 367.0.0 today. Please download latest gcloud version to work with Python 3.10.

for some reason running gcloud on it's own still produces error (on Mac)

~ ❯ gcloud --version                                       
Google Cloud SDK 367.0.0
beta 2021.12.10
bq 2.0.72
core 2021.12.10
gsutil 5.5
~ ❯ gcloud                                                   
ERROR: (gcloud) Command name argument expected.
ERROR: gcloud crashed (CommandLoadFailure): Problem loading gcloud.events: module 'collections' has no attribute 'MutableMapping'.

If you would like to report this issue, please run the following command:
  gcloud feedback

To check gcloud for common problems, please run the following command:
  gcloud info --run-diagnostics

Hi i could not reproduce the issue. could you please try fresh download the latest gcloud?

$ export CLOUDSDK_PYTHON=/Library/Frameworks/Python.framework/Versions/3.10/bin/python3
$ gcloud --version
Google Cloud SDK 367.0.0
bq 2.0.72
core 2021.12.10
gsutil 5.5

Thanks. I can reproduce it. We will work on a fix.

vinwong@ https://buganizer.corp.google.com/issues/202258405 is fixed.

for now, running gcloud without any parameters still throws an error.

vinwong@ we don't have full support for python 3.10 yet.

Thanks for your patience. Our product team confirmed that the issue has been fixed. Can you please check from your end of everything is okay?

It should work fine with python 3.10.

After updating my SDK to the latest version, the issue got resolved. Can you please try reinstalling the SDK if it doesn't solve the issue?

This issue tracker is a channel for reporting issues and requesting new features.

The issue you described looks like a technical issue and for troubleshooting, it would be best for you to contact the GCP support or to use the Community support.

This issue is still not resolved in version 371.0.0. As others have noted, the issue only occurs for certain commands/command groups. We are particularly impacted by the gcloud app command group being broken due to this issue (already noted above in comment #21), as it has made us unable to deploy some applications via our CI/CD pipelines.

It is surprising and frustrating that this issue has not been treated with more urgency. Having a command group break may not seem significant given the full breadth of services gcloud spans, but for some, a single broken command group means gcloud is effectively completely broken, because the vast majority of their usage is within that command group. Additionally, there are now three open issues for this bug (b/205238176 and b/216667499 being the others).

Version information and some failed commands are included below. Note that there are two different error messages, but both are caused by the same underlying issue.

> python -V
Python 3.10.2

> gcloud --version
Google Cloud SDK 371.0.0
alpha 2022.01.28
beta 2022.01.28
bq 2.0.73
cloud_sql_proxy 1.27.0
core 2022.01.28
gsutil 5.6

> gcloud
ERROR: (gcloud) Command name argument expected.
ERROR: gcloud failed to load (gcloud.interactive): Problem loading gcloud.interactive: cannot import name 'Mapping' from 'collections' (/Users/.../.pyenv/versions/3.10.2/lib/python3.10/collections/__init__.py).
[...]

> gcloud app
ERROR: (gcloud.app) Command name argument expected.
ERROR: gcloud crashed (CommandLoadFailure): Problem loading gcloud.app.deploy: module 'collections' has no attribute 'Mapping'.
[...]

As of 371.0.0, there are 8 unresolved issues that require patching. Patch file attached; online link below:

https://github.com/sudoforge/pkgbuilds/blob/master/google-cloud-sdk/0004-collections-abc.patch

Somewhat hilariously, 370.0.0 actually introduced the removal of a workaround to support the collections -> collections.abc change for newer versions of Python.

➜ diff {369,370}/platform/bq/bigquery_client.py | head -10
--- 369/platform/bq/bigquery_client.py    1980-01-01 01:00:00.000000000 -0700
+++ 370/platform/bq/bigquery_client.py    1980-01-01 01:00:00.000000000 -0700
@@ -58,9 +58,6 @@

 _GCS_SCHEME_PREFIX = 'gs://'

-collections_abc = collections
-if sys.version_info > (3, 8):
-  collections_abc = collections.abc

As of 372.0.0, there are unresolved issues in 8 different files that require patching. Patch file attached; online link below:

https://github.com/sudoforge/pkgbuilds/blob/master/google-cloud-sdk/0004-collections-abc.patch

Hello,

Thanks for your patience. Can you please provide us with some error trace logs?

With each new release lacking a fix, I publish a patch file containing fixes for the errors that I'm able to find. I do not utilize each and every command, so I am not currently able to provide a stack trace containing usage of each of the methods that my patch fixes.

If you are for some reason unable to view the patch and correlate the patches to broken areas of the codebase, I'd be happy to write a script to invoke a matrice of each gcloud subcommand with all of its flag variations. Requesting this seems... silly.

You can look at the patch file I provide with each update to determine whether or not the issue is fixed.

Oh, I missed this thread.

As of 373.0.0, there are unresolved issues in 6 different files that require patching. Patch file attached; online link below:

https://github.com/sudoforge/pkgbuilds/blob/master/google-cloud-sdk/0004-collections-abc.patch

As of google-cloud-sdk v374.0.0, there are six files that require patching. Patch file attached; online link below.

https://github.com/sudoforge/pkgbuilds/blob/50e777465b1b925941ca938e3174a34bc3fc8da8/google-cloud-sdk/0004-collections-abc.patch

As of google-cloud-sdk v375.0.0, there are six files that require patching. Patch file attached; online link below.

https://github.com/sudoforge/pkgbuilds/commit/50e777465b1b925941ca938e3174a34bc3fc8da8/google-cloud-sdk/0004-collections-abc.patch

Hello,

Thanks for your patience. I've forwarded the information provided by you to our product team and they are reviewing the issue.

As of google-cloud-sdk v376.0.0, there are six files that require patching. Patch file attached; online link below.

https://github.com/sudoforge/pkgbuilds/commit/50e777465b1b925941ca938e3174a34bc3fc8da8/google-cloud-sdk/0004-collections-abc.patch

I honestly can't believe the (lack of) response that this issue has received. Can we get an answer from a developer advocate or project manager as to why this issue has not been addressed over the past six months, and why this project does not target the latest mainline release of Python when many of its users' systems far supersede the officially supported versions?

Hello,

Thank you for your patience.

Circling back to our message on the 04 of March, the Product team is currently working on this issue and all necessary changes. We will keep you updated regarding the progress in this thread.

Please note that we don't have any ETA at this time.

Kind regards

Hello Everyone,

Thank you for your patience.

According to the product team, this issue has been fixed with the recent deployment of the Cloud SDK version 377.0.0. I'd recommend you to try upgrading your SDK to the mentioned version and checking if the issue was indeed fixed on your end and if not update us on this track.

That all being said, and since the issue has been marked as resolved internaly I will also mark this Bug Report as Fixed. Nevertheless if that is not the case for you please comment and this can be reopened.

As of google-cloud-sdk v378.0.0, there are six files that require patching. Online link below.

https://github.com/sudoforge/pkgbuilds/blob/59a45fed70948175d49fe1b85415ce7fb2786872/google-cloud-sdk/0004-collections-abc.patch

Hi,

According to the product team the code that you are patching is not reachable by any gcloud command. There is no engineering work to be done and no gcloud command is not working because of the issues brought up in this issue tracker. If there is an actual command that is not working and you have any further information reproducing the issue please re-open this tracker. I am closing this tracker as of now as the issue has been fixed with the recent version of the Cloud SDK.