Bug 1774942
Summary: | Booting from image causes OCI runtime error, "context deadline exceeded" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christophe de Dinechin <dinechin> |
Component: | kata-runtime | Assignee: | Christophe de Dinechin <dinechin> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 32 | CC: | crobinso, dinechin, fidencio |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-21 10:23:36 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christophe de Dinechin
2019-11-21 10:21:02 UTC
Hey Cole, I wonder if you had tested this configuration Ouptut of dmesg with `enable_debug=true` is not that informative: [2818435.190330] IPv6: ADDRCONF(NETDEV_CHANGE): vethf3835a1d: link becomes ready [2818435.190409] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [2818435.196248] cni-podman0: port 1(vethf3835a1d) entered blocking state [2818435.196250] cni-podman0: port 1(vethf3835a1d) entered disabled state [2818435.196322] device vethf3835a1d entered promiscuous mode [2818435.196396] cni-podman0: port 1(vethf3835a1d) entered blocking state [2818435.196397] cni-podman0: port 1(vethf3835a1d) entered forwarding state [2818435.438314] eth0: Caught tx_queue_len zero misconfig [2818438.450773] cni-podman0: port 1(vethf3835a1d) entered disabled state [2818438.456599] device vethf3835a1d left promiscuous mode [2818438.456608] cni-podman0: port 1(vethf3835a1d) entered disabled state Yes I tested this config, as mentioned before this is what the kernel nvdimm request is about: https://bugzilla.redhat.com/show_bug.cgi?id=1750581 https://bugzilla.redhat.com/show_bug.cgi?id=1696481 Without those modules built into the kernel, image= has no chance of working at the moment. That's likely the root issue. Unfortunately debugging these things with kata is a real pain. The way I did it, was to extract a qemu command to run manually, then I had easier options to capture appliance boot output, pass kernel arguments, also pass a custom initrd with dracut-systemd and systemd-initrd modules, and the 'rescue' boot option, which gives a way to inspect the appliance state. This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. As on Fedora we've decided to not use the image, but only the initrd method (see https://src.fedoraproject.org/rpms/kata-osbuilder/c/bd4294598d9dfb5807b8b2490c870dd2ebf9cf32?branch=master) we can close this one as WONTFIX. If there's the need to revisit this in the future, let's just re-open it without any issue. |