Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add egress rule to SG for TF 0.5 compat #920

Merged
merged 1 commit into from
May 8, 2015
Merged

Conversation

phinze
Copy link
Contributor

@phinze phinze commented May 8, 2015

armon added a commit that referenced this pull request May 8, 2015
Add egress rule to SG for TF 0.5 compat
@armon armon merged commit 774e8d1 into master May 8, 2015
@armon armon deleted the tf-module-0.5-compat branch May 8, 2015 18:20
@armon
Copy link
Member

armon commented May 8, 2015

LGTM!

duckhan pushed a commit to duckhan/consul that referenced this pull request Oct 24, 2021
With the introduction of tproxy, the errors when a connection fail
include the KubeDNS names, for example:

```
curl: (7) Failed to connect to test-er1l1u-consul-ingress-gateway.default port 8080: Connection refused
```

Rather than match on the name it's connecting to, we can instead rely on
the "curl: (7) Failed to connect" part of the string since error code 7
is always a connection refused error and that's all we're really
testing.

This is the specific test that was failing:
https://app.circleci.com/pipelines/github/hashicorp/consul-helm/2850/workflows/f145253b-2068-47d4-a427-b1ad7be6275c/jobs/11011.
I think it only passed before because it must have been getting "curl:
(52) Empty reply from server".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants