-
Bug
-
Resolution: Done
-
High
-
OSC 1.5.2
-
None
-
False
-
None
-
False
-
-
Bug Fix
-
Proposed
-
-
-
Kata Sprint #250
-
0
-
0
Description
We brought up OSC and deployed kata-config post which all the pods under the namespace openshift-sandboxed-containers-operator came into running state.
saripallilavanya@Lavanyas-MacBook-Pro Ansible-OpenShift-Provisioning % oc get pods -n openshift-sandboxed-containers-operator
NAME READY STATUS RESTARTS AGE
controller-manager-669f66cf87-bh7tt 2/2 Running 0 46h
openshift-sandboxed-containers-monitor-57mk4 1/1 Running 0 45h
openshift-sandboxed-containers-monitor-hm54w 1/1 Running 0 45h
peer-pods-webhook-696fb9b8c9-4wtmf 1/1 Running 0 45h
peer-pods-webhook-696fb9b8c9-6qrv6 1/1 Running 0 45h
peerpodconfig-ctrl-caa-daemon-28zt2 1/1 Running 0 10s
peerpodconfig-ctrl-caa-daemon-s4mg7 1/1 Running 0 6s
podvm qcow2 image used is stored under below volumes
[root@a3elp61 ~]# virsh vol-list --pool sl-pp-image Name Path ------------------------------------------------------------------------------ sl-8.9-commit-vol /var/lib/libvirt/images/sl-pp-img-dir/sl-8.9-commit-vol sl-9.2-commit-vol /var/lib/libvirt/images/sl-pp-img-dir/sl-9.2-commit-vol sl-pp-image-vol /var/lib/libvirt/images/sl-pp-img-dir/sl-pp-image-vol [root@a3elp61 ~]#
when we tried to bring up simple workload with kata runtime class as in below yaml
apiVersion: v1 kind: Pod metadata: name: nginx-pod spec: runtimeClassName: kata-remote containers: - name: nginx-container image: nginx:latest ports: - containerPort: 80
pod remained in container creation state.
saripallilavanya@Lavanyas-MacBook-Pro Ansible-OpenShift-Provisioning % kubectl get pod NAME READY STATUS RESTARTS AGE nginx-pod 0/1 ContainerCreating 0 8s
pod event says below
Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 20s default-scheduler Successfully assigned default/nginx-pod to workerv2-rr-1 Warning FailedCreatePodSandBox 19s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: remote hypervisor call failed: rpc error: code = Unknown desc = failed to inspect netns /var/run/netns/089d50dc-d328-4748-975e-738688a3fafa: failed to identify the host primary interface: failed to identify destination interface of default gateway on network namespace "/proc/1/task/13/ns/net": unknown Warning FailedCreatePodSandBox 18s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: remote hypervisor call failed: rpc error: code = Unknown desc = failed to inspect netns /var/run/netns/ee8c5880-c339-4f9c-b810-0bbb6cca42ef: failed to identify the host primary interface: failed to identify destination interface of default gateway on network namespace "/proc/1/task/13/ns/net": unknown Normal AddedInterface 4s (x3 over 19s) multus Add eth0 [10.128.2.21/23] from ovn-kubernetes Warning FailedCreatePodSandBox 4s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: remote hypervisor call failed: rpc error: code = Unknown desc = failed to inspect netns /var/run/netns/ee5b7098-ecee-41b1-92e0-ff6a7d49b541: failed to identify the host primary interface: failed to identify destination interface of default gateway on network namespace "/proc/1/task/14/ns/net": unknown
OCP versions 4.14 and 4.15 were tried along with OSC versions 1.5.0,1.5.1 and 1.5.2. Results were the same as of above.
- links to
-
RHBA-2024:129695
RHBA: sandboxed-containers bug fix and enhancement update
- mentioned on
