-
Notifications
You must be signed in to change notification settings - Fork 239
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] rhdh container segfaults on startup with CRC on Intel Mac #4087
Comments
is this running on an Intel or M-based mac? |
Per Issue subject; Intel Mac. Right now there are no aarch images for RHDH. |
On M1 it would have to run emulated, which might trigger an issue. It seems the |
Parallels, using Apple Virtualization Framework as it's engine. |
I was not able to reproduce this on my intel macbook, but it's still using macos12, so maybe that's why
|
I also can't reproduce after upgrading my intel macbook to macos13 Tim has run more tests, booting the crc VM using https://github.com/crc-org/vfkit/blob/main/contrib/scripts/start-crc-bundle.sh does not result in a crash, it's only when running the VM through CRC (and thus with the cluster running) that the crash occurs. @reestr Another test I'd be curious about is to reproduce the bug with crc ( |
I also can't reproduce it on my intel macbook to macos14.4
crc with openshift preset running as expected.
Get the expected output when running rhdh container
|
Can you please share which version of OpenShift/CoreOS crc is running? |
I am using the released crc 2.33 which comes with 4.14.12
|
After having a quick sync-up with @reestr following is the observation
Looks like something to do with kubelet service and rhdh container and it is only happen with @reestr`s system. On my mac every single time it succeed (no segfault) |
@reestr summary was slightly different
|
@cfergeau in terms of unreleased bundle (till then) yes, but with released bundle (4.14.12) it is same. With 4.15.3 there is other observation where even without kubelet start it failed 2-3 times but then succeed after that multiple time. But with kubelet started it only succeed once and failed multiple time. |
General information
crc setup
before starting it (Yes/No)? YesCRC version
CRC status
DEBU CRC version: 2.33.0+c43b17 DEBU OpenShift version: 4.14.12 DEBU Podman version: 4.4.4 DEBU Running 'crc status' CRC VM: Running OpenShift: Running (v4.14.12) RAM Usage: 8.573GB of 50.51GB Disk Usage: 31.62GB of 214.1GB (Inside the CRC VM) Cache Usage: 178.9GB Cache Directory: /Users/trees/.crc/cache
CRC config
Host Operating System
Steps to reproduce
podman run registry.redhat.io/rhdh/rhdh-hub-rhel9:1.1-97
Expected
Container succesfully starts, only presenting javascript error when probing for plugins.
Actual
Container does not start correctly, it instead segfaults.
Logs
No crc logs beyond starting:
Journal for the CRC VM shows the segfault:
Podman output:
Journal for the CRC VM shows the segfault:
[root@crc-vlf7c-master-0 /]# podman start registry.redhat.io/rhdh/rhdh-hub-rhel9:1.1-97Error: no container with name or ID "registry.redhat.io/rhdh/rhdh-hub-rhel9:1.1-97" found: no such container[root@crc-vlf7c-master-0 /]# podman run registry.redhat.io/rhdh/rhdh-hub-rhel9:1.1-97Loading config from MergedConfigSource{FileConfigSource{path="/opt/app-root/src/app-config.yaml"}, FileConfigSource{path="/opt/app-root/src/app-config.example.yaml"}, FileConfigSource{path="/opt/app-root/src/app-config.example.production.yaml"}, EnvConfigSource{count=0}}[root@crc-vlf7c-master-0 /]#
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.This issue is specific to CRC on MacOS, there are reports of rhdh running as expected on CRC with Fedora 39.
I am not able to reproduce this issue using a Vanilla Fedora 39 Server install with Podman using Parallels (Apple Virtulization Framework) with the same hardware (Intel MacOS). RHDH runs as expected on this.
The text was updated successfully, but these errors were encountered: