[jira] [Commented] (BEAM-7764) Dataflow run fails when service account is not set.

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-7764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174684#comment-17174684 ] 

Beam JIRA Bot commented on BEAM-7764:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Dataflow run fails when service account is not set.
> ---------------------------------------------------
>
>                 Key: BEAM-7764
>                 URL: https://issues.apache.org/jira/browse/BEAM-7764
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, sdk-go
>            Reporter: Nick Rucci
>            Priority: P2
>              Labels: dataflow, golang, stale-P2
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The dataflow runner is not setting the service account for the job that is being set up. This causes failures when trying to deploy.
> ```
>  Workflow failed. Causes: There was a problem refreshing your credentials. Please check:
> 1. Dataflow API is enabled for your project.
> 2. There is a robot service account for your project:
> service-[project number]@dataflow-service-producer-prod.iam.gserviceaccount.com should have access to your project. If this account does not appear in the permissions tab for your project, contact Dataflow support.
> ```
> Adding a flag to set the service account will fix this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)