-
Notifications
You must be signed in to change notification settings - Fork 243
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] x509 ingress controller error when connecting from macOS #3375
Comments
I'm happy to talk in Google Chat if that's easier. I'd love to help solve this for others if they're experiencing it too. |
This is fixed by crc-org/snc#578 |
I just tried it with 2.9.0 directly on macOS and the issue is still present. I'll try to change my writeup, it was just a lot of work collecting that the first time. I wish I had automated it 😅 Interesting that the issue was with the client though. I guess that's a good workaround. I know it's not strictly relevant to CRC, but if you know what certs I'd need to export from the cluster, I'd be happy to manually import and trust them until there's a fix. |
Oh, it also looks like the fix wasn't in the release, or isn't working? $ uname -a; crc version
Darwin m1a1 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:23 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64
CRC version: 2.9.0+589ab2cd
OpenShift version: 4.11.3
Podman version: 4.2.0 |
Can you check |
Ah! I thought crc-org/snc#578 was talking about downgrading the cluster, not the client. The dev env setup we have for our project automatically downloads the latest. I knew it was 4.11, and was about to manually downgrade. I'll use the version that came with CRC now. Maybe I'll even add a "I'm using CRC" option to our setup script. Thank you for helping with this, this has been bothering me for a long time. This should definitely be in the "Known Issues" section for CRC, since many folks won't read the openshift release notes in addition to them. But it looks like the release notes / docs haven't been updated for a few releases? |
Looks like anyone using crc properly won't hit this, so it's already fixed :) |
Note:
crc
-related information is on the linux machine, andoc
-related information is on the macOS machine.I also embedded various files and log outputs for convenience. I can move them to a gist if you wish.
I actually wrote this up for the first time on September 12th but never posted it. Now that the M1 is finally supported, I tried running it locally on my mac-- and I'm getting the same error!
General information
oc
from macOS.crc setup
before starting it (Yes/No)? YesCRC version
OC version
CRC status
CRC config
Host Operating System
Linux
macOS
topology details
There are three machines, each with different purposes:
oc
from it. Let's call this onemac
crc
. Let's call this onelinux
.dnsmasq
). Let's call this onedns-linux
.All three machines use the third for DNS configuration.
They are connected over
tailscale
, although that shouldn't matter much.Other relevant config files
kubeconfig on linux
~/.crc/machines/crc/kubeconfig
resolv.conf on linux machine (crc host)
linux /etc/resolv.conf
macos dns config
mac /etc/resolv.conf
``` # # macOS Notice # # This file is not consulted for DNS hostname resolution, address # resolution, or the DNS query routing mechanism used by most # processes on this system. # # To view the DNS configuration used by this system, use: # scutil --dns # # SEE ALSO # dns-sd(1), scutil(8) # # This file is automatically generated. # search TAILSCALE_USERNAME_REDACTED.beta.tailscale.net apps-crc.testing api.crc.testing ISP_DNS_DOMAIN_REDACTED nameserver 100.100.100.100 ```scutil --dns
dnsmasq on linux-dns
/etc/dnsmasq.conf
/etc/dnsmasq.d/crc.conf
haproxy on linux
/etc/haproxy/haproxy.cfg
Steps to reproduce
Note: these steps are simplified since it started happening locally on macOS too.
I can rewrite this issue to reflect that, but it's a lot of work to expose the same issue.
crc setup
crc console --credentials
Expected behavior: I am successfully logged in.
Actual behavior: x509 errors.
oc login on linux
oc login on mac
Logs
Before beginning, I ran
crc delete -f; rm -rf ~/.crc/
, and downloaded a fresh version ofcrc
.crc setup
linux$ crc setup --log-level 9
crc start
linux$ crc start --log-level=9
The text was updated successfully, but these errors were encountered: