ubuntu_blktrace_smoke_test failed on J-gkeop (BLKTRACESETUP(2) /dev/loop5 failed: 25/Inappropriate ioctl for device)

[Po-Hsu Lin]

Issue found on J-gkeop 5.15.0-1002.4

ubuntu_blktrace_smoke_test will timeout on all instances because of:
 BLKTRACESETUP(2) /dev/loop5 failed: 25/Inappropriate ioctl for device

 Running '/home/ubuntu/autotest/client/tests/ubuntu_blktrace_smoke_test/ubuntu_blktrace_smoke_test.sh'
 FAILED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-5.15.0-1002-gkeop)

 Using block device /dev/loop5 for path /home/ubuntu/autotest/client/results/default/ubuntu_blktrace_smoke_test.blktrace-smoke-test/mnt

 Test regime:
   dd performing 65536 1K block writes
   looking for at least 1024 blktrace events

 Mon Aug 29 10:41:37 UTC 2022: blktrace starting
 Mon Aug 29 10:41:37 UTC 2022: dd starting
 BLKTRACESETUP(2) /dev/loop5 failed: 25/Inappropriate ioctl for device
 Mon Aug 29 10:41:41 UTC 2022: dd stopped
 Mon Aug 29 10:41:41 UTC 2022: waiting for 10 seconds
 Mon Aug 29 10:41:51 UTC 2022: blktrace being terminated
 Timer expired (1200 sec.), nuking pid 4774
        ERROR ubuntu_blktrace_smoke_test.blktrace-smoke-test ubuntu_blktrace_smoke_test.blktrace-smoke-test timestamp=1661770898 localtime=Aug 29 11:01:38 Test timeout expired, rc=15

This is not a regression, it can be found with J-gkeop 5.15.0-1001.2 as well.

[Po-Hsu Lin (cypressyew)]

The kernel config check will fail on this kernel, looks like we don't have it enabled.
FAILED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-5.15.0-1002-gkeop)

Maybe we should fail the test when this config check is failing.