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

BF2 is not converted to nic mode after applied converting machineConfig

XMLWordPrintable

    • Critical
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Manually set bf2 card as dpu mode and apply converting MachineConfig, it should be converted to nic mode after nodes reboot, but it still stays in dpu mode.

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

      4.12

      How reproducible:

       

      Steps to Reproduce:

      1. Add label to workers  
      oc label node worker-05 node-role.kubernetes.io/sriov=   
      oc label node worker-47 node-role.kubernetes.io/sriov=
      2. Apply the machineConfig yaml metions in epic https://issues.redhat.com/browse/NHE-202 
      3. Workers will be rebooted as they are changed to NIC mode.
      4. After reboot connect to workers via ssh
      ssh core@192.168.122.119
      5. sudo podman run --pull always --replace --pid host --network host --user 0 --name bf -dit --privileged -v /dev:/dev quay.io/bnemeth/bf
      6. After run the get command should return "nic"
      7.sudo podman exec -it bf ./get_mode
      dpu

      Actual results:

      after applied machineconfig and nodes reboot,./get_mode still get dpu not nic.

      Expected results:

      bf2 should be converted to nic mode.

      Additional info:

       

              bnemeth@redhat.com Balazs Nemeth
              rhn-support-yingwang Ying Wang
              Ying Wang Ying Wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: