Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-10688

ovn-controller-ovs in CrashLoopBackOff due to empty conf.db

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • None
    • None
    • ovn-operator
    • None
    • 2
    • Neutron Sprint 2, Neutron Sprint 3, Neutron Sprint 4, Neutron Sprint 5
    • 4
    • Moderate

      The ovn-controler-ovs-<HASH> is in CrashLoopBackOff on the init container.

      Its logs show:
      $ oc logs ovn-controller-ovs-7wvtp -c ovsdb-server-init

      + CTL_ARGS='--system-id=random --no-ovs-vswitchd'
      + /usr/share/openvswitch/scripts/ovs-ctl start --system-id=random --no-ovs-vswitchd
      ovsdb-tool: ovsdb error: /etc/openvswitch/conf.db: cannot identify file type
      Starting ovsdb-server ovsdb-server: server configuration failed
      [FAILED]
      And going in debug mode into the init container shows that the file is empty.

      This was tested using the latest upstream operators.

          1.
          		 Root cause parent bug OSPRH-10688 Sub-task Closed Normal Unassigned

              ykarel@redhat.com Yatin Karel
              geguileo@redhat.com Gorka Eguileor
              Bharath M V Bharath M V
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: