-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 5.0
-
Fix Version/s: 5.0
-
Component/s: R-CORD
-
Labels:None
-
Story Points:3
New vSG instance that was created did not spin up the container as it lacked external connectivity.
Issue was observed on a QA Soak POD, (Flex was installed with master build and was up for almost 8 days). After a week of POD uptime, two new instances of vSG were created and one of them had the issue.
After further debugging by Scott and Jono, it was noticed that `hosts` of `onos-cord` did not have an entry for the newly created instance. Restarting the VTN synchronizer did not solve the issue. Jono states that there might timing of the calls to ONOS while adding service ports.
============================
2018-01-31 20:08:29,810 | WARN | ew I/O worker #4 | PacketManager | 127 - org.onosproject.onos-core-net - 1.10.10 | Packet processor org.opencord.cordvtn.impl.CordVtnArpProxy$InternalPacketProcessor@3a6f1af0 threw an exception
