NCP Operator Error while achieving port with specific address for node <master-node-name>: no port matches address [<ip-address>]

Products

• VMware NSX

Issue/Introduction

• The below error is seen when listing the cluster operator from OpenShift side:

#oc get co

NAME               VERSION    AVAILABLE    PROGRESSING     DEGRADED     SINCE  MESSAGE
nsx-ncp            0.0.3      True         False           True         2y79d  Error while achieving port with specific address for node master_node.domain: no port matches addresses [X.X.X.X]

• DHCP is being used to automatically assign IP addresses to OpenShift master/worker nodes.
• Default IP Discovery Segment Profile is linked to the segment where the master node is connected.
• The actual master node IP address cannot be found in the View Realized Bindings of the master node segment port.
  
  • You can also check the realized bindings using the following API:
    
    GET https://<NSX-Manager-IP-or-FQDN>/policy/api/v1/infra/segments/<master-node-segment>/ports/default:<id>/state
    
    Output:
    

      "realized_bindings" : [ {
        "source" : "ARP_SNOOPING",
        "binding" : {
          "ip_address" : "Y.Y.Y.Y", <<<<<<<<<<<<< it should show the actual master node IP X.X.X.X
          "mac_address" : "00:00:00:00:00:00",
          "vlan" : 0
        },

Environment

OpenShift running NSX NCP plugin 

Cause

When using the default IP discovery profile (TOFU enabled), IP address changes are not allowed. It means, only 1 ARP binding is allowed.

Resolution

There are multiple workarounds for this issue:

• Reboot the node.
• Or renew the DHCP lease on the node, this will make the DHCP binding refresh the "realized binding" table.
• If none of the above works, you can change the IP discovery profile to allow more than 1 ARP binding, this will make the "discovered binding" for X.X.X.X to become "Realized".

Additional Information

Understanding IP Discovery Segment Profile