-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Fixed
-
Affects Version/s: VOLTHA v2.8, VOLTHA v2.9
-
Fix Version/s: VOLTHA v2.8, VOLTHA v2.9
-
Component/s: openonu-adapter
-
Labels:None
-
Environment:
Sporadically observed in reconcilement regression tests. Problems only occur in case the MDS counter is not matching. In these tests this is more a rare exception.
Seen e.g. here:
https://jenkins.opencord.org/view/All%20Jobs/job/periodic-voltha-multiple-olts-openonu-go-test-bbsim/384/
-
Story Points:3
-
Epic Link:
There can be a mutex dead lock situation at reconcilement in case the available techProfile and flow is to be sent to the ONU via OMCUI configuration (MDS counter mismatch).
In this case the techProfile and flow configuration takes steadily mutex mutexPersOnuConfig for the complete time of state machine run until completion. This collides with the reception of OMCI frames in case the responses from OMCI inidcate that the MDS counter needs to be updated (which also uses mutex mutexPersOnuConfig). Waiting for mutexPersOnuConfig here blocks the complete reception of OMCI messages on mutexRxSchedMap, so that the received responses can also not be processed anymore to let the TechProfile/Flow processing proceed.
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
26420,1 | [VOL-4266] OpenOnuAdapter reconcile deadlock when configuring TechProfile/Flow on OMCI | master | voltha-openonu-adapter-go | Status: MERGED | +2 | +1 |
26421,1 | [VOL-4266] R2.8 OpenOnuAdapter reconcile deadlock when configuring TechProfile/Flow on OMCI | voltha-2.8 | voltha-openonu-adapter-go | Status: MERGED | +2 | +1 |