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

nodeip-configuration not enabled for VSphere UPI

XMLWordPrintable

    • No
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • Hide
      In {product-title} (product-version}, the `nodeip-configuration` service is now enabled on vSphere user-provisioned infrastructure cluster. This service determines the network interface controller (NIC) that {product-title} uses for communication with the Kubernetes API server when the node boots. In rare circumstances the service might select an incorrect node IP after an upgrade. If this happens, you can use the `NODEIP_HINT` feature to restore the original node IP, as described in the "Troubleshooting network issues" section of the documentation. (link:https://issues.redhat.com/browse/OCPBUGS-11068[*OCPBUGS-11068*])
      Show
      In {product-title} (product-version}, the `nodeip-configuration` service is now enabled on vSphere user-provisioned infrastructure cluster. This service determines the network interface controller (NIC) that {product-title} uses for communication with the Kubernetes API server when the node boots. In rare circumstances the service might select an incorrect node IP after an upgrade. If this happens, you can use the `NODEIP_HINT` feature to restore the original node IP, as described in the "Troubleshooting network issues" section of the documentation. (link: https://issues.redhat.com/browse/OCPBUGS-11068 [* OCPBUGS-11068 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-4963. The following is the description of the original issue:
      —
      Description of problem:

      After further discussion about https://issues.redhat.com/browse/RFE-3383 we have concluded that it needs to be addressed in 4.12 since OVNK will be default there. I'm opening this so we can backport the fix.

The fix for this is simply to alter the logic around enabling nodeip-configuration to handle the VSphere-unique case of platform type == "vsphere" and the VIP field is not populated.

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
2.
3.

      Actual results:

       

      Expected results:

       

      Additional info:

       

              bnemec@redhat.com Benjamin Nemec
              openshift-crt-jira-prow OpenShift Prow Bot
              Rio Liu Rio Liu
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: