+++ This bug was initially created as a clone of Bug #2016988 +++ Description of problem: AWS Nitro instances need special tuning for NVME devices, see: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#timeout-nvme-ebs-volumes Version-Release number of selected component (if applicable): 4.9 and 4.10 How reproducible: Always. Steps to Reproduce: 1. echo "cat /sys/module/nvme_core/parameters/io_timeout" | oc debug node/<node_name> Actual results: OS-provided value not equal to 4294967295 Expected results: 4294967295 Additional info: https://github.com/openshift/cluster-node-tuning-operator/pull/283
$ oc get nodes NAME STATUS ROLES AGE VERSION ip-10-0-131-10.us-east-2.compute.internal Ready master 93m v1.22.0-rc.0+a44d0f0 ip-10-0-133-11.us-east-2.compute.internal Ready worker 87m v1.22.0-rc.0+a44d0f0 ip-10-0-161-253.us-east-2.compute.internal Ready worker 86m v1.22.0-rc.0+a44d0f0 ip-10-0-179-175.us-east-2.compute.internal Ready master 93m v1.22.0-rc.0+a44d0f0 ip-10-0-204-46.us-east-2.compute.internal Ready worker 86m v1.22.0-rc.0+a44d0f0 ip-10-0-217-1.us-east-2.compute.internal Ready master 93m v1.22.0-rc.0+a44d0f0 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-10-28-150616 True False 72m Cluster version is 4.9.0-0.nightly-2021-10-28-150616 $ for node in $(oc get nodes --no-headers | cut -f 1 -d ' ' ); do echo $node; echo ""; echo "cat /sys/module/nvme_core/parameters/io_timeout" | oc debug node/$node; done ip-10-0-131-10.us-east-2.compute.internal Starting pod/ip-10-0-131-10us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.131.10 If you don't see a command prompt, try pressing enter. 4294967295 Removing debug pod ... ip-10-0-133-11.us-east-2.compute.internal Starting pod/ip-10-0-133-11us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.133.11 If you don't see a command prompt, try pressing enter. 4294967295 Removing debug pod ... ip-10-0-161-253.us-east-2.compute.internal Starting pod/ip-10-0-161-253us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.161.253 If you don't see a command prompt, try pressing enter. 4294967295 Removing debug pod ... ip-10-0-179-175.us-east-2.compute.internal Starting pod/ip-10-0-179-175us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.179.175 If you don't see a command prompt, try pressing enter. 4294967295 Removing debug pod ... ip-10-0-204-46.us-east-2.compute.internal Starting pod/ip-10-0-204-46us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.204.46 If you don't see a command prompt, try pressing enter. 4294967295 Removing debug pod ... ip-10-0-217-1.us-east-2.compute.internal Starting pod/ip-10-0-217-1us-east-2computeinternal-debug ... To use host binaries, run `chroot /host` Pod IP: 10.0.217.1 If you don't see a command prompt, try pressing enter. 4294967295 Removing debug pod ...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.6 bug fix 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/RHBA-2021:4119