concourse-pipeline-resource icon indicating copy to clipboard operation
concourse-pipeline-resource copied to clipboard

Fails in 6.1.0

Open pikesley opened this issue 4 years ago • 2 comments

With reference to #71 I am now testing Concourse 6.1.0. I have removed the tag so I'm using the latest version of this resource, but now in the check I get:

run check step: run check step: check: resource script '/opt/resource/check []' failed: exit status 1

stderr:
Logging to /tmp/concourse-pipeline-resource-check.log692886880
2020/05/21 15:06:04 exit status 1 - error: resource not found

Am I doing something dumb?

pikesley avatar May 21 '20 15:05 pikesley

And I cannot hijack the container to inspect those logs:

↳ fly -t six hijack --check pipeline/existing-pipelines
error: 400 Bad Request websocket: bad handshake

This is running on a GKE cluster with nginx ingress

pikesley avatar May 26 '20 16:05 pikesley

For the "400 Bad Request websocket" error, try enabling websocket support in ingress controller, by adding following annotation to your ingress (for example via concourse helm chart values if you are installing Concourse using Helm)

web:
  ingress:
    annotations:
      nginx.org/websocket-services: concourse-web

prein avatar Oct 22 '20 16:10 prein