#3314 imm: Deadlock between pbe and ccb applied on a pbe object

[Hieu Hong Hoang]

Generally, a critical ccb won't be processed if the pbe doesn't start and we can't set implementer to an object if exists an active ccb which applies on that object. In this issue, an active ccb applied on an pbe object and was in critical state while pbe wasn't start. The system failed to start pbe because that ccb is active and the ccb wasn't be processed because the pbe wasn't start. It is a deadlock here.

Log analysis:

• pbe failed to start:

<143>1 2022-05-02T14:57:51.553529+02:00 SC-1 osafimmnd 389 osafimmnd [meta sequenceId="58624"] 389:imm/immnd/ImmModel.cc:15066 TR TRY_AGAIN: ccb 4 is active on object 'opensafImm=opensafImm,safApp=safImmService' bound to OI name 'OpenSafImmPBE'. Can not set re-attach implementer
2022-05-02 14:57:51.554 SC-1 osafimmpbed: ER saImmOiImplementerSet for OpenSafImmPBE failed 6

• ccb was blocked in critical state

2022-05-02 14:57:52.534 SC-1 osafimmnd[389]: WA Timeout (6) on transaction in critical state! ccb:4
2022-05-02 14:57:52.534 SC-1 osafimmnd[389]: WA There are ccbs blocked in critical state, waiting for pbe process to re-attach as OI

[Hieu Hong Hoang]

commit 1542758ef4637321b987bd67becac66bcccca06d (ticket-3314)
Author: hieu.h.hoang hieu.h.hoang@dektech.com.au
Date: Mon May 2 12:56:23 2022 +0700

imm: Fix pbe deadlock [#3314]

Immpbe will fail to restart if a ccb which applies to an immpbe object
changes state to critical. The ccb will be aborted if immpbe restarts
successful. Unfortunately, the pbe couldn't restart if there is an active
ccb in an immpbe object. Solution is to allow immpbe to start even if
there is an active ccb in an immpbe object.