Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-103910

[Azure][azure-vm-utils] backport "queue/io_timeout=240" to remote NVMe disks

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • azure-vm-utils-0.7.0-1.el10
    • No
    • Low
    • TestOnly
    • rhel-virt-cloud
    • ssg_virtualization
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • No
    • None
    • Unspecified Release Note Type - Unknown
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      Right now we are using a kernel parameter "nvme_core.io_timeout=240" which takes effect on all NVMe disks. It's in fact only needed for remote NVMe disks - stated by Karl Abbott.

      Fortunately, azure-vm-utils has this parameter set. We need to 1. backport this and 2. remove the above kernel parameter after backport (need a separate ticket for OSbuild Composer).

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      How reproducible is this bug?:

      Steps to reproduce

      1.  
      2.  
      3.  

      Expected results

      Actual results

              rhn-support-huzhao Huijuan Zhao
              litian@redhat.com Li Tian
              virt-maint virt-maint
              Xiaoqiang Xiong Xiaoqiang Xiong
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: