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

[Alicloud] sdn2ovn migration rollback failed on network operator not available

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 4.12
    • Node / Kubelet
    • Important
    • OCPNODE Sprint 230 (Blue), OCPNODE Sprint 238 (Blue)
    • 2
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      [Alicloud] sdn2ovn migration rollback failed on network operator not available
      

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

      4.12.0-0.nightly-2022-12-19-150237

      How reproducible:

      Always

      Steps to Reproduce:

      1. Run sdn2ovn migration script in Alicloud: https://github.com/openshift/release/blob/master/ci-operator/step-registry/ovn/sdn-migration/ovn-sdn-migration-commands.sh
      2. Run sdn2ovn migration rollback script in Alicloud: https://github.com/openshift/release/blob/master/ci-operator/step-registry/ovn/sdn-migration-rollback/ovn-sdn-migration-rollback-commands.sh
      
      

      Actual results:

      Only network operator is not available

      Expected results:

      network operator is available

      Additional info:

      After rollback, the 80-openshift-network.conf is missing under /etc/cni/net.d . But it exists under /var/run/multus/cni/net.d/ .

      Attachments

        1. kubelet_crio.log
          5.86 MB
        2. master-node.log
          5.03 MB
        3. worker-node.log
          3.03 MB

        Issue Links

          Activity

            People

              harpatil@redhat.com Harshal Patil
              weliang1@redhat.com Weibin Liang
              Zhanqi Zhao Zhanqi Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: