Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-6858

Missing CRI-O version dependency leads to network not starting

XMLWordPrintable

    • None
    • uShift Sprint 231
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

       

      Version-Release number of selected component (if applicable):

      V4.12 RC3

      How reproducible:

      every time

      Steps to Reproduce:

      1. setup ostree image build system without RHOCP V4.12 beta repository 
2. build ostree image, boot that 
3.

      Actual results:

      startup fails with "network not starting":
Jan 09 08:44:18 edgenius microshift[3052]: kubelet E0109 08:44:18.070252    3052 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"ovnkube-node-g86hk_openshift-ovn-kubernetes(3ea3925d-f3ba-4623-b3c8-9bb8c658f130)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"ovnkube-node-g86hk_openshift-ovn-kubernetes(3ea3925d-f3ba-4623-b3c8-9bb8c658f130)\\\": rpc error: code = Unknown desc = error creating pod sandbox with name \\\"k8s_ovnkube-node-g86hk_openshift-ovn-kubernetes_3ea3925d-f3ba-4623-b3c8-9bb8c658f130_0\\\": invalid policy in \\\"/etc/containers/policy.json\\\": Unknown key \\\"keyPaths\\\"\"" pod="openshift-ovn-kubernetes/ovnkube-node-g86hk" podUID=3ea3925d-f3ba-4623-b3c8-9bb8c658f130

      Expected results:

      clean startup

      Additional info:

       

              rnoriega@redhat.com Ricardo Noriega De Soto
              dfroehli42rh Daniel Fröhlich
              John George John George
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: