在过去的两个月中,我们的IAM用户/角色设置已经成功地允许BigTable访问。
在过去的两天中,我们遇到了用户帐户的权限错误(服务帐户仍然可以访问BigTable)
我们在web UI中遇到了用户权限错误:
{
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}

并在使用来自
"com.google.cloud.bigtable" % "bigtable-hbase-1.x"堆栈跟踪:
Caused by: io.grpc.StatusRuntimeException: PERMISSION_DENIED: The caller does not have permission
at io.grpc.Status.asRuntimeException(Status.java:517)
at com.google.cloud.bigtable.grpc.async.AbstractRetryingOperation.onError(AbstractRetryingOperation.java:165)
at com.google.cloud.bigtable.grpc.async.AbstractRetryingOperation.onClose(AbstractRetryingOperation.java:143)
at com.google.cloud.bigtable.grpc.scanner.RetryingReadRowsOperation.onClose(RetryingReadRowsOperation.java:203)
at com.google.cloud.bigtable.grpc.io.ChannelPool$InstrumentedChannel$2.onClose(ChannelPool.java:210)
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:41)
at com.google.cloud.bigtable.grpc.io.RefreshingOAuth2CredentialsInterceptor$UnAuthResponseListener.onClose(RefreshingOAuth2CredentialsInterceptor.java:416)最近有没有更严格执行https://cloud.google.com/bigtable/docs/access-control中列出的permissions的变化-那么我们是否应该更新IAM角色?
编辑1:已尝试更新角色以包括以下内容;但仍出现相同的错误:

编辑2:三天后;问题解决了,谷歌将访问权限恢复到原来的工作状态(用户账户可以再次看到数据)。
发布于 2017-12-12 06:18:19
https://stackoverflow.com/questions/47752477
复制相似问题