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

4.11 [iavf] It takes long time to create multiple VF interfaces and the VF interface names are not consistent [rhel-8.6.0.z]

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.11.z
    • RHCOS
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Fix for https://bugzilla.redhat.com/show_bug.cgi?id=2163259 needs to ship to OCP clusters, weekly kernel build already has a fix included. We need to ship as part of OCP 4.12.2 release and include the kernel build in RHCOS image.

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

       

      How reproducible:

       

      Steps to Reproduce:

      1. Install ocp 4.12.2
      2. Make sure kernel version is kernel-4.18.0-372.43.1.el8_6 

      Actual results:

       

      Expected results:

       

      Additional info:

       

            [OCPBUGS-7034] 4.11 [iavf] It takes long time to create multiple VF interfaces and the VF interface names are not consistent [rhel-8.6.0.z]

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Important: OpenShift Container Platform 4.11.27 security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2023:0651

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Important: OpenShift Container Platform 4.11.27 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:0651

            $ oc get clusterversion
            NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
            version   4.11.0-0.nightly-2023-02-07-165722   True        False         79s     Cluster version is 4.11.0-0.nightly-2023-02-07-165722
            $ oc get nodes
            NAME                                       STATUS   ROLES    AGE     VERSION
            ci-ln-7tjbtf2-72292-vrx9p-master-0         Ready    master   18m     v1.24.6+263df15
            ci-ln-7tjbtf2-72292-vrx9p-master-1         Ready    master   19m     v1.24.6+263df15
            ci-ln-7tjbtf2-72292-vrx9p-master-2         Ready    master   19m     v1.24.6+263df15
            ci-ln-7tjbtf2-72292-vrx9p-worker-a-dzv6r   Ready    worker   9m57s   v1.24.6+263df15
            ci-ln-7tjbtf2-72292-vrx9p-worker-b-86lzl   Ready    worker   9m57s   v1.24.6+263df15
            ci-ln-7tjbtf2-72292-vrx9p-worker-c-zzlmt   Ready    worker   10m     v1.24.6+263df15
            $ oc debug node/ci-ln-7tjbtf2-72292-vrx9p-worker-a-dzv6r
            Temporary namespace openshift-debug-wwmmc is created for debugging node...
            Starting pod/ci-ln-7tjbtf2-72292-vrx9p-worker-a-dzv6r-debug ...
            To use host binaries, run `chroot /host`
            Pod IP: 10.0.128.2
            If you don't see a command prompt, try pressing enter.
            sh-4.4# chroot /host
            sh-4.4# rpm-ostree status
            State: idle
            Deployments:
            * pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8ac779aeaf935e25e78bb20f824d04f9e55407dc271d9a55012ce6ed55e3d053
                          CustomOrigin: Managed by machine-config-operator
                               Version: 411.86.202302021552-0 (2023-02-02T15:55:31Z)
            sh-4.4# rpm -q kernel
            kernel-4.18.0-372.43.1.el8_6.x86_64
            sh-4.4# exit
            exit
            sh-4.4# exit
            exitRemoving debug pod ...
            Temporary namespace openshift-debug-wwmmc was removed.
            

            Michael Nguyen added a comment - $ oc get clusterversion NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS version   4.11.0-0.nightly-2023-02-07-165722   True        False         79s     Cluster version is 4.11.0-0.nightly-2023-02-07-165722 $ oc get nodes NAME                                       STATUS   ROLES    AGE     VERSION ci-ln-7tjbtf2-72292-vrx9p-master-0         Ready    master   18m     v1.24.6+263df15 ci-ln-7tjbtf2-72292-vrx9p-master-1         Ready    master   19m     v1.24.6+263df15 ci-ln-7tjbtf2-72292-vrx9p-master-2         Ready    master   19m     v1.24.6+263df15 ci-ln-7tjbtf2-72292-vrx9p-worker-a-dzv6r   Ready    worker   9m57s   v1.24.6+263df15 ci-ln-7tjbtf2-72292-vrx9p-worker-b-86lzl   Ready    worker   9m57s   v1.24.6+263df15 ci-ln-7tjbtf2-72292-vrx9p-worker-c-zzlmt   Ready    worker   10m     v1.24.6+263df15 $ oc debug node/ci-ln-7tjbtf2-72292-vrx9p-worker-a-dzv6r Temporary namespace openshift-debug-wwmmc is created for debugging node... Starting pod/ci-ln-7tjbtf2-72292-vrx9p-worker-a-dzv6r-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.128.2 If you don't see a command prompt, try pressing enter. sh-4.4# chroot /host sh-4.4# rpm-ostree status State: idle Deployments: * pivot: //quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8ac779aeaf935e25e78bb20f824d04f9e55407dc271d9a55012ce6ed55e3d053               CustomOrigin: Managed by machine-config- operator                    Version: 411.86.202302021552-0 (2023-02-02T15:55:31Z) sh-4.4# rpm -q kernel kernel-4.18.0-372.43.1.el8_6.x86_64 sh-4.4# exit exit sh-4.4# exit exitRemoving debug pod ... Temporary namespace openshift-debug-wwmmc was removed.

            The kernel with the fix has been picked up in 411.86.202302021552-0

            Scott Dodson added a comment - The kernel with the fix has been picked up in 411.86.202302021552-0

            Thanks for reporting your issue!

            In order for the CoreOS team to be able to triage your issue, please copy the applicable parts of the following template into a comment and fill them out as completely as possible.

            Be ready for follow-up questions and please respond in a timely manner.

            If we can't reproduce a bug, we might close your issue.


            OCP Version at Install Time:
            RHCOS Version at Install Time:
            OCP Version after Upgrade (if applicable):
            RHCOS Version after Upgrade (if applicable):
            Platform (AWS, Azure, bare metal, GCP, vSphere, etc.):
            Architecture (x86_64, ppc64le, s390x, etc.):

            If you're having problems booting/installing RHCOS, please provide:

            • Reproduction steps that work with a single RHCOS node
            • The full contents of the serial console showing disk initialization, network configuration, and Ignition stages. See this article for information about configuring your serial console. Screenshots or a video recording of the console is usually not sufficient.
            • Ignition JSON
            • Output of journalctl -b

            If you're having problems post-upgrade, please provide:

            • A complete must-gather (oc adm must-gather)

            If you're having SELinux related issues, please provide:

            • The full /var/log/audit/audit.log file
            • Were any SELinux modules or booleans changed from the default configuration?
            • The output of ostree admin config-diff | grep selinux/targeted on impacted nodes

            Please add anything else that might be useful, for example:

            • Kernel command line (cat /proc/cmdline)
            • Contents of /etc/NetworkManager/system-connections/
            • Contents of /etc/sysconfig/network-scripts/

            OpenShift Jira Bot added a comment - Thanks for reporting your issue! In order for the CoreOS team to be able to triage your issue, please copy the applicable parts of the following template into a comment and fill them out as completely as possible. Be ready for follow-up questions and please respond in a timely manner. If we can't reproduce a bug, we might close your issue. OCP Version at Install Time: RHCOS Version at Install Time: OCP Version after Upgrade (if applicable): RHCOS Version after Upgrade (if applicable): Platform (AWS, Azure, bare metal, GCP, vSphere, etc.): Architecture (x86_64, ppc64le, s390x, etc.): If you're having problems booting/installing RHCOS, please provide: Reproduction steps that work with a single RHCOS node The full contents of the serial console showing disk initialization, network configuration, and Ignition stages. See this article for information about configuring your serial console. Screenshots or a video recording of the console is usually not sufficient. Ignition JSON Output of journalctl -b If you're having problems post-upgrade, please provide: A complete must-gather ( oc adm must-gather ) If you're having SELinux related issues, please provide: The full /var/log/audit/audit.log file Were any SELinux modules or booleans changed from the default configuration? The output of ostree admin config-diff | grep selinux/targeted on impacted nodes Please add anything else that might be useful, for example: Kernel command line ( cat /proc/cmdline ) Contents of /etc/NetworkManager/system-connections/ Contents of /etc/sysconfig/network-scripts/

              mnguyen@redhat.com Michael Nguyen
              rhn-it-vlaad Vikas Laad
              Michael Nguyen Michael Nguyen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: