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

v2/tests: TestSQLServerAuthentication failed #2203

Closed
flaky-bot bot opened this issue Apr 23, 2024 · 4 comments
Closed

v2/tests: TestSQLServerAuthentication failed #2203

flaky-bot bot opened this issue Apr 23, 2024 · 4 comments
Assignees
Labels
flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Apr 23, 2024

Note: #2101 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.


commit: 3f9e2de
buildURL: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/8793786115
status: failed

@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Apr 23, 2024
Copy link
Author

flaky-bot bot commented Apr 23, 2024

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.


When run at the same commit (3f9e2de), this test passed in one build (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/8793786115) and failed in another build (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/8793786115).

@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Apr 23, 2024
@enocom
Copy link
Member

enocom commented Apr 23, 2024

connection_test.go:80: unable to verify proxy was serving: 2024/04/23 02:15:10 [] could not resolve instance version: fetch ephemeral cert failed: Refresh error: create ephemeral cert failed (connection name = ""): googleapi: got HTTP response code 502 with body:

Rate limiting error.

@enocom
Copy link
Member

enocom commented Apr 30, 2024

Will be fixed when GoogleCloudPlatform/cloud-sql-go-connector#781 is released.

@enocom
Copy link
Member

enocom commented Apr 30, 2024

Duplicate of #2144

@enocom enocom marked this as a duplicate of #2144 Apr 30, 2024
@enocom enocom closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants