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

[Mac] proxy_test.go failed in nightly run #4575

Closed
lilyLuLiu opened this issue Jan 17, 2025 · 4 comments
Closed

[Mac] proxy_test.go failed in nightly run #4575

lilyLuLiu opened this issue Jan 17, 2025 · 4 comments

Comments

@lilyLuLiu
Copy link
Contributor

Suspect this related to github.com/elazarl/goproxy v1.3.0 bump to 1.4.0: d31efeb

Enter [It] wait for cluster in Running state - /workspace/test/integration/proxy_test.go:74 @ 01/17/25 03:15:00.491
[FAILED] Unexpected error:
<*errors.errorString | 0x14000278240>:
not found: running. Timeout
{
s: "not found: running. Timeout",
}
occurred
In [It] at: /workspace/test/integration/proxy_test.go:76 @ 01/17/25 03:25:00.496
< Exit [It] wait for cluster in Running state - /workspace/test/integration/proxy_test.go:74 @ 01/17/25 03:25:00.496 (10m0.003s)
Enter [AfterAll] TOP-LEVEL - /workspace/test/integration/proxy_test.go:17 @ 01/17/25 03:25:00.496
< Exit [AfterAll] TOP-LEVEL - /workspace/test/integration/proxy_test.go:17 @ 01/17/25 03:25:01.225 (729ms)

@gbraad
Copy link
Contributor

gbraad commented Jan 17, 2025

@lilyLuLiu What are we trying to open here? as the request timed out in the proxy-service...

@praveenkumar
Copy link
Member

Suspect this related to github.com/elazarl/goproxy v1.3.0 bump to 1.4.0: d31efeb

I tried to see if that is the case and abstracted proxy.go to run independently which works without any issue so we need to figure out what that timeout issue is by trying crc manually?

@praveenkumar praveenkumar changed the title proxy_test.go failed in nightly run [Mac] proxy_test.go failed in nightly run Jan 17, 2025
@gbraad
Copy link
Contributor

gbraad commented Jan 17, 2025

perhaps a network-glitch? I have run into issues in recent time for service in the west-US region that timed out/didn't resolve.

@lilyLuLiu
Copy link
Contributor Author

Finally figured out this error was caused by WIP self-sufficient bundle[1] that accidentally uploaded to https://cdk-builds.usersys.redhat.com/builds/crc/bundles/ and replace the original 4.17.10 bundle.

[1] crc-org/snc#980
[2] discussion: https://redhat-internal.slack.com/archives/CGG67T45P/p1737093651504639

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

No branches or pull requests

3 participants