-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gsutil ImportError: cannot import name json_format #527
Comments
Looks like several versions ago, the Cloud SDK team added the google/protobuf package [1] into their bootstrapping scripts (used to launch gsutil and other tools). It seems that if your system has another / an older version of that package, it can take precedence over the verison gcloud includes with its bundle, causing this import error. If you have this module installed in your system python installation, try uninstalling it so that gcloud's version will be used. If you're on macOS and using homebrew, running |
Similar to what @gouglum said above, on a quite old VM my system actually had protobuf installed in I'm not sure if it's because I was upgrading from a very old gcloud (149) or if I somehow actually had installed protobuf into system packages earlier in the life of the VM. |
This effectively breaks gsutil on RHEL or Centos7. Is there any other to fix this other than removing the python-protobuf package? That package is needed on my systems for other purposes to removing it is not an option. |
I'm trying to use the
gsutil
command line tool to create a bucket, and I'm getting the following error:ImportError: cannot import name json_format
(full stack trace below). Even running a simplegsutil --help
causes this.I didn't have any such issues when using
gsutil
, and I can't remember any specific changes in my environment that could cause this error. All I remember was updatinggcloud components
to 201.0.0 before seeing this error. Anyway, I followed this suggestion on Stack Overflow to revert to gcloud components version 175.0.0 by runninggcloud components update --version 175.0.0
and this error goes anyway.When will we be able to use
gustil
ingcloud components
version 201.0.0? Or is there some configuration that I'm missing?Thanks and cheers!
The text was updated successfully, but these errors were encountered: