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:

in /usr/lib/udev/rules.d/80-azure-disk.rules of azure-vm-utils-0.7.0-1.el10

ENV{DEVTYPE}=="disk", ATTRS{nsid}=="?*", ATTR{queue/io_timeout}="240000" 

1. cat /proc/cmdline
   BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.0-151.el10.aarch64 root=UUID=eec314f7-81ad-4726-8ba3-5c14900440b3 ro nvme_core.io_timeout=240 console=ttyAMA0 crashkernel=2G-4G:406M,4G-64G:470M,64G-:726M

   How reproducible is this bug?:

   Steps to reproduce

2. install azure-vm-utils-0.7.0-1.el10
3.  check cat /proc/cmdline
4.  

Expected results

remove the  kernel parameter after it using

80-azure-disk.rules of azure-vm-utils-0.7.0-1.el10

Actual results

still has nvme_core.io_timeout=240  in kernel parameter