Manually adding and running the tests
If tests fail to plan because of hardware detection or other issues, contact Red Hat support to manually add a test.
On rare occasions, tests may fail to plan. This can happen due to problems with hardware detection or other issues with the hardware, OS, or test scripts. If this happens, you should get in touch with your Red Hat support contact for further assistance.
Support likely asks you to open a support ticket for the issue. Support then explains how to manually add a test to your local test plan. You add the test by using the rhcert-cli command on the HUT.
Any modifications you make to the local test plan is sent to the test server. You can continue to use the web interface on the test server to run your tests. The command is run as follows:
# rhcert-cli plan --add --test=<testname> --device=<devicename> --udi-<udi>
The options for the rhcert-cli command used here are:
- plan - Modify the test plan
- --add - Add an item to the test plan
- --test=<testname> - The test to be added. The test names are as follows:
- hwcert/suspend
- hwcert/audio
- hwcert/battery
- hwcert/lid
- hwcert/dpdk
- fast_datapath/ovs_dpdk
- hwcert/usbbase/expresscard
- hwcert/usbbase/usbbase/usb2
- hwcert/usbbase/usbbase/usb3
- hwcert/kdump
- hwcert/network/Ethernet/100MegEthernet
- hwcert/network/Ethernet/1GigEthernet
- hwcert/network/Ethernet/10GigEthernet
- hwcert/network/Ethernet/40GigEthernet
- hwcert/network/wlan/WirelessG
- hwcert/network/wlan/WirelessN
- hwcert/memory
- hwcert/core
- hwcert/cpuscaling
- hwcert/fvtest/fv_core
- hwcert/fvtest/fv_live_migration
- hwcert/fvtest/fv_memory
- hwcert/fvtest/fv_network
- hwcert/fvtest/fv_storage
- hwcert/fvtest/fv_pcie_storage_passthrough
- hwcert/fvtest/fv_pcie_network_passthrough
- hwcert/fvtest/fv_usb_storage_passthrough
- hwcert/fvtest/fv_usb_network_passthrough
- hwcert/fvtest/fv_cpu_pinning
- hwcert/profiler
- hwcert/storage
- hwcert/video
- hwcert/supportable
- hwcert/optical/bluray
- hwcert/optical/dvd
- hwcert/optical/cdrom
- hwcert/fencing
- hwcert/realtime
- hwcert/reboot
- hwcert/tape
- hwcert/rdma/Infiniband_QDR
- hwcert/rdma/Infiniband_FDR
- hwcert/rdma/Infiniband_EDR
- hwcert/rdma/Infiniband_HDR
- hwcert/rdma/Infiniband_Socket_Direct
- hwcert/rdma/10GigRoCE
- hwcert/rdma/20GigRoCE
- hwcert/rdma/25GigRoCE
- hwcert/rdma/40GigRoCE
- hwcert/rdma/50GigRoCE
- hwcert/rdma/100GigRoCE
- hwcert/rdma/200GigRoCE
- hwcert/rdma/10GigiWarp
- hwcert/rdma/20GigiWarp
- hwcert/rdma/25GigiWarp
- hwcert/rdma/40GigiWarp
- hwcert/rdma/50GigiWarp
- hwcert/rdma/100GigiWarp
- hwcert/rdma/200GigiWarp
- hwcert/rdma/Omnipath
- hwcert/network/Ethernet/2_5GigEthernet
- hwcert/network/Ethernet/5GigEthernet
- hwcert/network/Ethernet/20GigEthernet
- hwcert/network/Ethernet/25GigEthernet-
- hwcert/network/Ethernet/50GigEthernet
- hwcert/network/Ethernet/100GigEthernet
- hwcert/network/Ethernet/200GigEthernet
- rhcert/self-check
- hwcert/sosreport
- hwcert/storage/U2 SATA
- hwcert/storage/M2 SATA
- hwcert/storage/SATA_SSD
- hwcert/storage/SATA
- hwcert/storage/SAS_SSD
- hwcert/storage/SAS
- hwcert/storage/U2_NVME
- hwcert/storage/M2_NVME
- hwcert/storage/PCIE_NVME
- hwcert/storage/NVDIMM
- hwcert/storage/STORAGE
- The other options are only needed if a device must be specified. This applies to network and storage tests that need to know which device to run on. There are various places you would need to look to determine the device name or UDI that would be used here.
Support can help determine the proper name or UDI. Once found, you would use one of the following two options to specify the device:
+ ** --device=<devicename> - The device that should be tested, identified by a device name such as "enp0s25" or "host0".
+ ** --udi=<UDI> - The unique device ID of the device to be tested, identified by a UDI string. * Run the rhcert-cli command by specifying the test name:
+
rhcert-cli run --test=<test_name>
for example:
+
rhcert-cli run --test=audio
- You can specify
--deviceto run the specific device:rhcert-cli run --test=<test name> --device=<device name>for example:
rhcert-cli run --test=kdump --device=nfs
It is advisable to use rhcert-cli or rhcert-run independently and save the results. Mixing the use of both rhcert-cli and rhcert-run and saving the results together may cause errors. This mixing can result in the inability to process the results correctly.