-
Notifications
You must be signed in to change notification settings - Fork 232
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
[BUG] Ingress Https Port value not being used to update kubeconfig during crc start #4124
Comments
Do you have a webserver or some podman machine container, or 'something' listening on your macbook on port 443? |
You can set |
I have checked with the following cmd, and everything looks ok.
Tried it, unfortunately, I get another error down the line:
The cluster is running, but it cannot be accessed. |
This is something we fixed long time back, I am not sure why it is not checking with |
That is exactly the order in which I run the commands. |
Looks like there is some regression on our user mode networking side and I tried an older version of crc-2.28 (around that time I put that code for this logic 2484015 ) and it works but with latest version it doesn't even using same bundle which we ship with 2.28 (so it is not regression on bundle side but on the networking side). |
Based on the discussion, the issue is more about how
This particularly looks like a configuration issue when fetching the required token for updating kubeconfig (which should be available at port |
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
DEBU CRC version: 2.34.1+b470b5 DEBU OpenShift version: 4.15.3 DEBU Podman version: 4.4.4 DEBU Running 'crc status' CRC VM: Stopped OpenShift: Stopped (v4.15.3) RAM Usage: 0B of 0B Disk Usage: 0B of 0B (Inside the CRC VM) Cache Usage: 38.37GB Cache Directory: /Users/usrmb/.crc/cache
CRC config
- consent-telemetry : no
Host Operating System
Steps to reproduce
Expected
OpenShift cluster is started successfully
Actual
Following error is through while running the command crc start
failed to expose port :443 -> 192.168.127.2:443: listen tcp :443: bind: address already in use
Logs
The text was updated successfully, but these errors were encountered: