-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
System test for 'Topic.check_iam_permissions' fails with 503 #1687
Comments
Sorry my e-mail client didn't do a good job of filtering. Is this still a problem? What's the request body? |
@tmatsuo the request is now failing with a 400, rather than a 503: Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "gcloud/pubsub/topic.py", line 395, in check_iam_permissions
self.full_name, list(permissions))
File "gcloud/pubsub/connection.py", line 537, in test_iam_permissions
resp = conn.api_request(method='POST', path=path, data=wrapped)
File "gcloud/connection.py", line 343, in api_request
error_info=method + ' ' + url)
gcloud.exceptions.BadRequest: 400 The IAM operation failed with a non-retryable error: Unknown error. See https://cloud.google.com/pubsub/access_control for more information. (POST https://pubsub.googleapis.com/v1/projects/<MY-PROJECT-ID>/topics/<TOPIC-NAME>:testIamPermissions) The body of the request looks like so: {"permissions": ["roles/owner", "roles/editor", "roles/viewer"]} |
Oh I see. "roles/owner", "roles/editor", and "roles/viewer" are all
or something like that? |
I'm new to the IAM APIs, but I wonder if the following might be worth checking just in case:
Hmm, those were just shots in the dark. You shouldn't need admin permissions to check your permissions. Try @tmatsuo's suggestion first. That's probably it. |
…-samples#1687) * fixes vision delete dataset region tag * removes extra bracket
…-samples#1687) * fixes vision delete dataset region tag * removes extra bracket
While working on a new system test for
Topic.check_iam_permissions
(the wrapper forprojects.topics.testIamPermissions
), the back-end consistently fails the API call with a 503::@tmatsuo does that extra code (
8a75
) tell you anything about the failure?The text was updated successfully, but these errors were encountered: