[
https://issues.apache.org/jira/browse/BEAM-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774291#comment-16774291
]
Valentyn Tymofieiev commented on BEAM-6706:
-------------------------------------------
[~kenn], I would say that there isn't enough sufficient information in this
thread to determine rootcause of the issue, and one needs to investigate
further why the Dataflow pipeline is stuck. The first message and one by
[~mattcasters_neo4j] are concerning since seems like migration from 2.9.0 to
2.10.0 is at least not smooth, but there is also not enough information in this
thread to understand the rootcause.
> User reports trouble downloading 2.10.0 Dataflow worker image
> -------------------------------------------------------------
>
> Key: BEAM-6706
> URL: https://issues.apache.org/jira/browse/BEAM-6706
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
>
> DataFlow however is throwing all sorts of errors. For example:
> * Handler for GET
> /v1.27/images/gcr.io/cloud-dataflow/v1beta3/beam-java-batch:beam-2.10.0/json
> returned error: No such image:
> gcr.io/cloud-dataflow/v1beta3/beam-java-batch:beam-2.10.0"
> * while reading 'google-dockercfg' metadata: http status code: 404 while
> fetching url
> http://metadata.google.internal./computeMetadata/v1/instance/attributes/google-dockercfg";
> * Error syncing pod..."
> The job gets stuck after starting a worker and after an hour or so it gives
> up with a failure. 2.9.0 runs fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
