Open pkesseli opened 2 years ago
This looks similar to #3294, as per start logs it is also failed to renew the certificates.
this is an SFF system. Does the CPU throttle under load?
It's an Intel Core i7 4790, it supports thermal throttling, so certainly possible. I guess if as a response to https://github.com/code-ready/crc/issues/3294 you add support for custom timeouts during this renewal, this should address my issue as well and we can close this ticket.
These timeouts are part of OpenShift. We do not have any control over this :-/ Let's continue in the other issue. OK?
For the timeout issue that makes sense, but just to double-check: Before I hit the timeout there is also a DNS error in my log.
Check DNS query from host...
Failed to query DNS from host: lookup foo.apps-crc.testing: no such host
This was the original reason why I created this issue. Is this expected for the same reason as the TLS renewal or does this sound like a network / DNS issue on Windows 10 / Hyper-V?
We haven't been impacted by this for quite some time. The last was https://github.com/code-ready/crc/issues/1193 and we resolved this by directly using the hosts file. Check the entries in c:\windows\system32\drivers\etc\hosts
. Is there and entry for the foo.apps-crc.testing
hostname?
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 have this issue, it doesn't really affect me, but it seems like an oversight to look for a hard-coded namespace like "foo" in the startup. The whole Red Hat OpenShift Local feels sketchy as hell.
My local system has 32 cores and 64GB of ram... so not slow at all.
I have exactly the same issue here
INFO Check DNS query from host...
WARN Failed to query DNS from host: lookup foo.apps-crc.testing: no such host
using
PS C:\> crc version
time="2022-12-06T16:19:12+01:00" level=warning msg="Could not load system CA pool: crypto/x509: system root pool is not available on Windows"
WARN Could not load system CA pool: crypto/x509: system root pool is not available on Windows
CRC version: 2.11.0+a5f90a25
OpenShift version: 4.11.13
Podman version: 4.2.0
WARN Failed to query DNS from host: lookup foo.apps-crc.testing: no such host
is expected behaviour, so this is not indicating any specific issues with your crc install. This warning has been removed in git.
Can you file a new issue and provide the information from the issue template so that we can investigate what's going on?
thanks for making clear that the mentioned warning is expected behaviour.
meanwhile I found the cause of my DNS problems. crc is not the only software on my machine manipulationg the hosts file. VMWare was/is writing rules to the same line in the hosts ...and that line became too long
it would be good if the tools would write each rule in a seperate line.....
We have code to make sure the line does not get too long, but maybe we don't catch what vmware is doing to it :-/
General information
crc setup
before starting it (Yes/No)?CRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
GUI:
crc-windows-amd64.msi
Console:
crc-windows-amd64.msi
Expected
Check DNS query from host...
passes, OpenShift starts and is able to download images from DockerHub.Actual
In addition to this,
Verifying validity of the kubelet certificates...
fails. In the GUI version CRC tries to start again from scratch, in the console version it exits with an error. https://console-openshift-console.apps-crc.testing/ is available and new projects can be configured, but any pod will fail to download images from DockerHub, whether or not I configure an image pull credential.Logs
Before gather the logs try following if that fix your issue
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.crc-start-log-level-debug.log