Open GoogleCodeExporter opened 8 years ago
Update: tried running "gcloud compute instances list" again after updating the
Google Cloud SDK and got this error:
$ gcloud compute instances list
ERROR: gcloud crashed (UnicodeDecodeError): 'ascii' codec can't decode byte
0xe2 in position 1438: ordinal not in ran
ge(128)
Original comment by richardk...@gmail.com
on 27 Jan 2016 at 2:53
Thanks for the update. Please post the stack trace from the log that contains
the UnicodeDecodeError.
Original comment by gsfow...@google.com
on 27 Jan 2016 at 12:45
2016-01-27 12:53:20,449 DEBUG root Loaded Command Group:
['gcloud', 'compute']
2016-01-27 12:53:20,496 DEBUG root Loaded Command Group:
['gcloud', 'compute', 'instances']
2016-01-27 12:53:21,120 DEBUG root Loaded Command Group:
['gcloud', 'compute', 'instances', 'list']
2016-01-27 12:53:21,169 ERROR ___FILE_ONLY___ BEGIN CRASH STACKTRACE
Traceback (most recent call last):
File "/usr/local/share/google/google-cloud-sdk/lib/googlecloudsdk/gcloud_main.py", line 169, in main
gcloud_cli.Execute()
File "/usr/local/share/google/google-cloud-sdk/lib/googlecloudsdk/calliope/cli.py", line 655, in Execute
print_error=True)
File "/usr/local/share/google/google-cloud-sdk/lib/googlecloudsdk/calliope/cli.py", line 705, in _HandleKnownErr
or
msg = u'({0}) {1} {2}'.format(command_path_string, unicode(exc),
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1438:
ordinal not in range(128)
2016-01-27 12:53:21,170 ERROR root gcloud crashed
(UnicodeDecodeError): 'ascii' codec can't decode b
yte 0xe2 in position 1438: ordinal not in range(128)
2016-01-27 12:53:21,170 INFO ___FILE_ONLY___
If you would like to report this issue, please run the following command:
2016-01-27 12:53:21,170 INFO ___FILE_ONLY___ gcloud feedback
Original comment by richardk...@gmail.com
on 27 Jan 2016 at 12:55
Hello, is anyone looking into this? Three days seems like a long time to let
this issue go unaddressed! I think it goes without saying, but being to create
new VMs that can use Google Cloud APIs is kind of a core feature. If this
doesn't get fixed soon I'm going to have to find a different place to host my
service!
Original comment by richardk...@gmail.com
on 30 Jan 2016 at 2:44
I need to get this fixed by Monday morning JST. I didn't choose that date, it
just has to be done. If it is not resolved, I won't be able to use Google Cloud
Platform anymore, as sad as that makes me. Someone from technical support told
me engineers were looking into this but haven't heard anything since. Could I
please get some kind of status update?
Original comment by richardk...@gmail.com
on 30 Jan 2016 at 3:21
Update: Now I'm getting the access denied error from my existing VMs - not just
the new ones I create. The last log I have of a server being able to
successfully access Google APIs was at 2016-01-30 12:33:58 GMT.
Original comment by richardk...@gmail.com
on 30 Jan 2016 at 12:51
Original issue reported on code.google.com by
richardk...@gmail.com
on 27 Jan 2016 at 1:52