VxRail: Node health-check fails for test 'idc-q' (iDRAC Queue)

VxVerify runs multiple tests on each node by uploading a 'minion' heath-check program, which detects issues that may cause upgrades to fail. One of these node health-checks is 'idc_q', which clears outstanding commands from the iDRAC queue and reports back the success of the clearance operation*.

This health-check returns one of the following results:

If the iDRAC commands timeout or get an invalid response, then other iDRAC based tests are likely to fail too, such as 'idc_as' (iDRAC Admin State).
An example of the health-check output, when iDRAC is not responding, is shown below:

#========================#======#=========#====================================================================#==============#
|  Hostname / Category   |Status  Dell_KB |  Warnings or Failures, unless tests Passed                         ; Product S.N. |
#========================#======#=========#====================================================================#==============#
| Node1                  | Failure  43184 | idc_q: iDRAC queries failed                                                      .|

* Unless the -s or --service argument is added when running VxVerify. This argument is also included when VxVerify is run as part of LCM or ADC.

The 'idc-q' test queries whether there are queued upgrade jobs are on the iDRAC. If any jobs are present, the details of these are saved to the VxVerify logs, and then the queue is cleared.

Clearing the queues can be bypassed by running VxVerify with the --service (-s) option, which runs the minion script without restarting the Platform Service.

For the following events: iDRAC queries failed

If VxVerify is run with the default upgrade profile, it attempts to fix iDRAC communication issues by restarting iDRAC and iSM. See article:

• Dell VxRail: health-check 'ism_fix' or 'rac_fix' attempting to automatically correct Dell iSM and iDRAC issues