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

firmware search path is not automatically configured in OCP (KMM)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 4.17.0
    • kmm
    • None
    • None
    • Proposed
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      In case kernel modules needs to use a dedicated firmware, KMM operator sets those files under /var/lib/firmware path. This path is not a default search path for firmware files, so KMM needs to configure the kernel to use this path via /sys/module/firmware_class/parameters/path. for this KMM uses setFirmwareClassPath field of the KMM config. By default this field is not set, so in order to set it customer needs to manually change change the configmap and then delete KMM operator pods.

       

        

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              bthurber@redhat.com Brett Thurber
              yshnaidm Yevgeny Shnaidman
              Lital Alon Lital Alon
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: