-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Low
-
Resolution: Done
-
Affects Version/s: VOLTHA v2.9
-
Fix Version/s: VOLTHA v2.9
-
Component/s: openonu-adapter
-
Labels:None
-
Environment:
Investigated in a failed patch verification jenkins job:
https://jenkins.opencord.org/job/verify_voltha-openonu-adapter-go_sanity-test/1372/
But I think I saw similar problems already in other normal jenkins verification jobs, without having analyzed that in detail by now.
Log from above job attached.Investigated in a failed patch verification jenkins job: https://jenkins.opencord.org/job/verify_voltha-openonu-adapter-go_sanity-test/1372/ But I think I saw similar problems already in other normal jenkins verification jobs, without having analyzed that in detail by now. Log from above job attached.
-
Story Points:2
-
Epic Link:
ONU soft reboot is always accompagnied by an according ONU down indication.
Depending on ONU adapter internal processing sequences either the direct reboot request processing is finished first or the ONU indication down processing. It can't really be assumed that one or the other is finished first.
But current code at the moment unconditionally sets the ONU connection state to 'reachable' at the end of the reboot processing. That is then the final static state seen from the system in case the ONU down indication processing had been finished already before that.
As in that state the ONU is really down, the state 'reachable' is not really expected.
OnuAdapter code must be updated to best not touch the ONU connection state at the end of the soft-reboot processing.
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 29101,4 | [VOL-4459] ONU connection state may be wrong or misleading after ONU soft reboot | master | voltha-openonu-adapter-go | Status: MERGED | +2 | +1 |
| 30193,2 | [VOL-4459] ONU connection state may be wrong or misleading after ONU soft reboot | voltha-2.8 | voltha-openonu-adapter-go | Status: MERGED | +2 | +1 |
