Comment 3 for bug 1864906

This issue is not service or customer impacting but can intermittently affect product verification BMC test execution.

In this case the BMC access method (bm_type) was changed from a fixed value of redfish or ipmi to 'dynamic'.

Dynamic mode tells maintenance to try Redfish but default to IPMI if Redfish appears to not be supported, i.e. fails.

The failure was in the handling of the bm_type reprovisioning change called for in the PV stress test.

The bm_type change caused the maintenance code to relearn the BMC access method which failed when it found that the thread was already running. The maintenance code does not distinguishing a thread launch failure with a Redfish protocol failure during BMC protocol discovery nor does it retry like it would normally do for other operations.

The fix is to improve thread launch failure handling during BMC protocol discovery.

The real impact is that if we don't fix this issue then the product verification BMC stress/regression test might fail occasionally like it did here.