-
Notifications
You must be signed in to change notification settings - Fork 242
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
CRC networking degrades #2597
Comments
Interesting! Thanks for the bug report. I will try tomorrow. When it happens, can you still reach the console or run oc commands? |
Yes, I can load console just fine and run all oc commands as well. Timeouts only happen when some service talks to the internet from within the cluster. To my naive mind, I think something goes wrong with |
I am running the VM for 1.5h on my mac right now and it works. Can you look at the output of Can you try to avoid the DNS resolution when you test? Maybe do a curl to an IP. |
I tried during 5h and I didn't face the issue. I also ran periodically Apache Bench on a static website to eventually trigger the issue. |
Sorry, I haven't worked with CRC in the last couple of days so haven't had a chance to gather the requested info. I'll likely be able to do it early next week.
Do you mena you were able to reproduce the issue with Apache Bench? FWIW, I'm using OpenTelemetry collector that exports a bunch of metrics to a remote endpoint (SignalFx) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I am also seeing something similar Inside the VM I was able to curl both Quay.io and also redhat so the VM it self appears to have network access but when attempting to use podman we see the error: curl
podman
From outside the VM
Originally raised in #3373 |
Hi @IBMRob - are you running on |
Description
CRC cluster on my Macbook laptop runs into networking issues after a few minute of uptime. Usually everything works perfectly for anywhere between 10-20 minutes and then all of a sudden HTTP requests to internet start failing with timeout errors. When this happens, I can still make the same requests from the host (laptop) and they work. I do not run any proxy or VPN. The issues seem to affect most things such as custom services I run in the cluster or cluster's ability to pull new images from quay.
Sometimes restarting a cluster helps but most of the time I have to delete the cluster, run the cleanup command and start a new one to fix the issue. As a result, I'm never able to test/develop/debug services and operators on OpenShift for more than ~15 minutes.
General information
OS: macOS
Hypervisor: hyperkit
Did you run
crc setup
before starting it (Yes/No)?Yes.
Running CRC on: Laptop / Baremetal-Server / VM
Laptop (Intel Macbook Pro)
CRC version
CodeReady Containers version: 1.29.1+bc5f4409 OpenShift version: 4.7.18 (not embedded in executable)
CRC status
CRC config
Host Operating System
Steps to reproduce
Expected
Networking to continue to work under all circumstances.
Actual
After 15-20 mins, most HTTP requests start failing. Calling remote endpoints manually starts failing. The cluster also fails to pull images with timeout errors. Some times restarting the cluster and the stay icon fixes it but most of the time I have to delete the cluster, run
crc cleanup
and start a new one to fix it only to run into the same issue again in another 15-20 minutes.Logs
Before gather the logs try following if that fix your issue
If I make the same requests from my laptop instead of from within the CRC cluster, it works.
At the time of reporting this issue, I had changed nameserver to 8.8.8.8 but I've experienced the same issue for weeks before setting the nameserver.
The text was updated successfully, but these errors were encountered: