Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-75598

Inconsistent IP Reporting in OpenShift Console for Virtual Machines

XMLWordPrintable

    • Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None

      The OpenShift Web Console does not display the correct IP addresses for Virtual Machines using multiple network interfaces, specifically when combining the default Pod network, Cluster User Defined Networks (CUDN), and secondary networks with localnet topology.

      Environment

      • Platform: OpenShift Container Platform (OCP) 4.19
      • Operator: OpenShift Virtualization (CNV) 4.19.15
      • Networking Plugin: OVN-Kubernetes
      • Interface Count: 3 (1x Pod Network, 1x CUDN, 1x NAD Localnet)

      Steps to Reproduce

      1. Create a CUDN with Layer3 topology (Role: Secondary) as defined in the provided YAML.
      2. Create a NetworkAttachmentDefinition (NAD) using ovn-k8s-cni-overlay with localnet topology.
      3. Deploy a Virtual Machine with three interfaces mapping to:
      • default pod network.
      • first-cudn (ClusterUserDefinedNetwork).
      • br-ex-network (NAD localnet).

      Navigate to the Virtualization -> VirtualMachines -> [VM Name] -> Network Interfaces tab in the OpenShift Console.

      Expected Behavior

      The console should display the assigned IPv4 (and IPv6, if applicable) for all three interfaces. Specifically:

      • The Pod Network interface should show the assigned cluster-internal IP.
      • The CUDN interface should show the IP assigned from the 10.100.0.0/16 range.
      • The Localnet interface should show the actual IP assigned via the external bridge/DHCP.

      Actual Behavior

      • Pod Network: The IP address is missing/blank in the dashboard view.
      • CUDN Interface: Does not display the real assigned IP.
      • Localnet Interface: Displays an incorrect/link-local IPv6 address instead of the primary IP address.

      Supporting Information

      CUDN Configuration:

      apiVersion: k8s.ovn.org/v1
      kind: ClusterUserDefinedNetwork
      metadata:
        name: first-cudn
      spec:
        namespaceSelector:
          matchExpressions:
          - key: kubernetes.io/metadata.name
            operator: In
            values: ["test-vms"]
        network:
          layer3:
            role: Secondary
            subnets:
            - cidr: 10.100.0.0/16
              hostSubnet: 24
          topology: Layer3 

      NAD Configuration:

      apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        name: br-ex-network
        namespace: default
      spec:
        config: '{ "name":"br-ex-network", "type":"ovn-k8s-cni-overlay", "cniVersion":"0.4.0", "topology":"localnet", "netAttachDefName":"default/br-ex-network" }' 

      Will share the link for screenshots in the comments section.
       
       

              phoracek@redhat.com Petr Horacek
              rhn-support-dpateriy Divyam Pateriya
              Kedar Bidarkar Kedar Bidarkar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: