-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.0
-
Component/s: Deprecated - VOLTHA, Deprecated - vOLTHA HA, ofagent-py
-
Labels:None
-
Story Points:5
-
Epic Link:
-
Sprint:VOLTHA 2.0 Sprint 8
When running a K8s cluster setup
Forcing the deletion of the vcore pod will lead to another one recreated on a different node of the cluster. OFagent is out of sync at this point and declares 0 device to ONOS. Bouncing the OFagent pod makes it recover.
Moving the vcore pod from one node to another is not tracked properly by OFagent (and maybe some other containers)
- is cloned by
-
-
- Resolved
-
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 11056,3 | VOL-1183: OFagent cannot reach vcore after vcore moved to different node in cluster | master | voltha | Status: MERGED | +2 | +1 |
