[
https://issues.apache.org/jira/browse/BEAM-6745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17122908#comment-17122908
]
Beam JIRA Bot commented on BEAM-6745:
-------------------------------------
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.
> Cannot run pipeline on Dataflow (GO SDK)
> ----------------------------------------
>
> Key: BEAM-6745
> URL: https://issues.apache.org/jira/browse/BEAM-6745
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, sdk-go
> Reporter: Michael Chemani
> Priority: P2
> Labels: stale-P2
>
> I got
> ```
> {{Failed to retrieve staged files: failed to retrieve worker in 3 attempts:
> bad MD5 for /var/opt/google/staged/worker: d79JZxFttnJG7SPkF30ozA==, want ;
> bad MD5 for /var/opt/google/staged/worker: d79JZxFttnJG7SPkF30ozA==, want ;
> bad MD5 for /var/opt/google/staged/worker: d79JZxFttnJG7SPkF30ozA==, want ;
> bad MD5 for /var/opt/google/staged/worker: d79JZxFttnJG7SPkF30ozA==, want}}
> ```
>
> When trying to run
> ```
> {{dataflow \ --runner dataflow \ --index gs://\{BUCKET}/data_100k.csv \
> --output gs://\{BUCKET}/ \ --project {PROJECT} \ --temp_location
> gs://\{BUCKET}/tmp/ \ --staging_location gs://\{BUCKET}/binaries/ \
> --worker_harness_container_image=apache-docker-beam-snapshots-docker.bintray.io/beam/go:20180515}}
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
