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

Multus: Host device pod network interface addition fails on s390x

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 4.17
    • Networking / multus
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          Multus: Host Device: when pod is creating with additional network interface using static configuration, network interface says attached but it won't show up in ip address list

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

          4.17 and previous 

      How reproducible:

          2/5

      Steps to Reproduce:

          1. Install 4.17.-ec-2 OCP build 
          2. create a service account and authorize the service account with privilege
          3. apply network definition attachment in a project namespace
      {noformat} apiVersion: k8s.cni.cncf.io/v1
      kind: NetworkAttachmentDefinition
      metadata:
        creationTimestamp: "2024-07-26T07:09:04Z"
        generation: 1
        name: host-device
        namespace: kitchen-sink-host-device
        ownerReferences:
        - apiVersion: operator.openshift.io/v1
          blockOwnerDeletion: true
          controller: true
          kind: Network
          name: cluster
          uid: 0d0c6e26-c5d7-48bd-aa8f-2cca4d8bec6d
        resourceVersion: "931673"
        uid: 0df33927-830f-4884-a00e-e7cf0f2b8b9c
      spec:
        config: '{ "cniVersion": "0.3.1", "name": "host-device", "type": "host-device",
          "device": "br-int", "ipam": { "type": "static", "addresses": [ { "address": "192.168.1.3/24"
          } ] } }' {noformat}
           4. create a pod with the above network config
      {noformat} 
      apiVersion: v1
      kind: Pod
      metadata:
        name: host-device
        namespace: kitchen-sink-host-device
        annotations:
          k8s.v1.cni.cncf.io/networks: |-
            [
              {
                "name": "host-device",
                "namespace": "kitchen-sink-host-device"
              }
            ]
      spec:
        serviceAccount: anyuid-sa
        containers:
          - name: test-host-container-1
            image: registry.redhat.io/rhel8/support-tools
            command: ["sleep", "infinity"] {noforamt}
           5. observed few warning FailedCreatePodSandBox while pod creation and describe of pod says net1 interface is configured with ip provided 
            

      Actual results:

          If we do rsh to the pod and ip address it doesn't show the net1 interface 

      Expected results:

          pod should should have net1 interface added when it comes up. 

              dosmith Douglas Smith
              apuranda Amrut Purandare
              None
              None
              Dominik Werle Dominik Werle
              None
              IBM Confidential Group
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: