-
Type: Bug
-
Status: Resolved (View Workflow)
-
Priority: High
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.1
-
Component/s: Deprecated - VOLTHA
-
Labels:
-
Story Points:8
-
Sprint:VOLTHA 2.1 Sprint 6
At startup, the ofagent sends a register() followed by StreamPacketsOut(), ReceivePacketsIn() and ReceiveChangeEvents() to open the streaming channel between the ofagent<>api-server and api-server<>corepair. The streaming channel remains open to allow for changed events and packetsIn/out to flow between the ofagent and the cores via the api-server. This works well.
If a core in a pair takes longer to start or is restarted then the streaming channel for changes events and packetsIn/out won't be setup to that Core. If that Core ends up receiving a createDevice, hence owning the device, then subsequent packetIns/Out and changed events won't make it to the ofagent/cores.
The suggestion is for the api-router to retry setting the streaming connection on failure.
- relates to
-
VOL-1661 when starting voltha, sometimes the api-server (afrouter) needs to be restarted to work. There shall not be startup dependency.
- Resolved