Skip to content
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.

Fails in 6.1.0 #73

Open
pikesley opened this issue May 21, 2020 · 2 comments
Open

Fails in 6.1.0 #73

pikesley opened this issue May 21, 2020 · 2 comments

Comments

@pikesley
Copy link

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
Copy link
Author

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

@prein
Copy link

prein commented Oct 22, 2020

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants