Description of problem:

using ansible-playbook test vsphere-4.13 migrate from SDN to OVNK, it will fail in checking Network Operator updating after patch networkType to OVNKubernetes

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

How reproducible:

Always

Steps to Reproduce:

1. ansible-playbook failed log

TASK [migration : Wait until MCO starts applying new machine config to nodes] *************************************************************************************************************************************
ok: [localhost] => {"changed": false, "msg": "MCO started updating nodes successfully."}

TASK [migration : Print MCO status message] ***********************************************************************************************************************************************************************
ok: [localhost] => {
    "msg": "MCO started updating nodes successfully."
}

TASK [migration : Wait for MCO to finish its work] ****************************************************************************************************************************************************************
[WARNING]: Retrying as got an error
ok: [localhost] => {"changed": false, "msg": "MCO finished successfully."}

TASK [migration : Verify machine configuration status on nodes] ***************************************************************************************************************************************************
ok: [localhost] => {"changed": false, "issues": [], "msg": "All machine configurations are correct."}

TASK [migration : Trigger OVN-Kubernetes deployment] **************************************************************************************************************************************************************
changed: [localhost] => {"changed": true, "msg": "Successfully triggered OVNKubernetes deployment.", "output": "network.config.openshift.io/cluster patched"}

TASK [migration : Wait until the Network Cluster Operator is in PROGRESSING=True state] ***************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Timeout waiting for Network Cluster Operator to reach PROGRESSING=True."}

PLAY RECAP ********************************************************************************************************************************************************************************************************
localhost                  : ok=22   changed=4    unreachable=0    failed=1    skipped=5    rescued=0    ignored=0   

2. after this failed and a long while, mcps still cannot do updating. only stay in below status:

oc get mcp                                                                                                    
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-da71290292755aff896a47a0863e05f9   True      False      False      3              3                   3                     0                      161m
worker   rendered-worker-99a8d25d75bc07260440e8609cfdc97c   True      False      False      2              2                   2                     0                      161m

3.

Actual results:

Expected results:

Additional info:

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms:

Is it an

1. internal CI failure
2. customer issue / SD
3. internal RedHat testing failure

If it is an internal RedHat testing failure:

• Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).

If it is a CI failure:

• Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
• Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
• Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
• When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
• If it's a connectivity issue,
• What is the srcNode, srcIP and srcNamespace and srcPodName?
• What is the dstNode, dstIP and dstNamespace and dstPodName?
• What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)

If it is a customer / SD issue:

• Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
• Don’t presume that Engineering has access to Salesforce.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
• Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
  • If the issue is in a customer namespace then provide a namespace inspect.
  • If it is a connectivity issue:
    • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What is the dstNode, dstNamespace, dstPodName and dstPodIP?
    • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
    • Please provide the UTC timestamp networking outage window from must-gather
    • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
  • If it is not a connectivity issue:
    • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.

• When showing the results from commands, include the entire command in the output.  
• For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
• For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components