[
https://issues.apache.org/jira/browse/BEAM-7764?focusedWorklogId=279217&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-279217
]
ASF GitHub Bot logged work on BEAM-7764:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jul/19 18:01
Start Date: 18/Jul/19 18:01
Worklog Time Spent: 10m
Work Description: lostluck commented on pull request #9092: [BEAM-7764]
Add the ability to set the service account email for dataflow jobs
URL: https://github.com/apache/beam/pull/9092
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 279217)
Time Spent: 1h 20m (was: 1h 10m)
> 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
> Assignee: Nick Rucci
> Priority: Major
> Labels: dataflow, golang
> Time Spent: 1h 20m
> 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
(v7.6.14#76016)
