You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running the 02c, pipleine.run, and got the following error:
"message: "Failed to create pipeline job. Error: Service account [email protected] does not have [storage.objects.get, storage.objects.create] IAM permission(s) to the bucket "learn-demo1". Please either copy the files to the Google Cloud Storage bucket owned by your project, or grant the required IAM permission(s) to the service account..""
It seems the service account does not have permission to the bucket, I've tried to change the role of the account from "Editor" to "owner" manually in the IAM section but it did not work.
The text was updated successfully, but these errors were encountered:
I recieved the same error, it gave me these instructions:
From the console link above, or by going to https:/console.cloud.google.com and navigating to "IAM & Admin > IAM":
Locate the row for the service account listed above: [email protected]
Under the inheritance column click the pencil icon to edit roles
In the fly over menu, under Assign roles select Add Another Role
Click the Select a role box and type Storage Object Admin, then select Storage Object Admin
Click Save
Rerun the list of services below and verify the role has been added.
I'm running the 02c, pipleine.run, and got the following error:
"message: "Failed to create pipeline job. Error: Service account
[email protected]
does not have[storage.objects.get, storage.objects.create]
IAM permission(s) to the bucket "learn-demo1". Please either copy the files to the Google Cloud Storage bucket owned by your project, or grant the required IAM permission(s) to the service account..""It seems the service account does not have permission to the bucket, I've tried to change the role of the account from "Editor" to "owner" manually in the IAM section but it did not work.
The text was updated successfully, but these errors were encountered: