-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.3
-
Component/s: etcd
-
Labels:
-
Story Points:3
-
Epic Link:
After deleting an OLT, some state related to the OLT remains in etcd. For example, here's a diff of the etcd state before and after running the "sanity test" with BBSim:
$ diff /tmp/before.dump /tmp/after.dump
0a1,2
> service/voltha/
>
18a21,32
> service/voltha/openolt/{b7b02e22a118d81111889d9f}/flowids_per_gem/{0}
> {"1024":[4],"1026":[6],"1027":[7,8,9,10]}
> service/voltha/openolt/{b7b02e22a118d81111889d9f}/flowids_per_gem/{4294967295}
> {"4294967295":[1,2,3]}
> service/voltha/owns_device_b7b02e22a118d81111889d9f
> voltha-rw-core-684d4675fd-65gp5
> service/voltha/resource_manager/{XGS-PON}/{b7b02e22a118d81111889d9f}/{0,-1,-1}/flow_ids
> []
> service/voltha/resource_manager/{XGS-PON}/{b7b02e22a118d81111889d9f}/{0,1}/alloc_ids
>
> service/voltha/resource_manager/{XGS-PON}/{b7b02e22a118d81111889d9f}/{0,1}/gemport_ids
>
Above, b7b02e22a118d81111889d9f is the ID of the OLT that was deleted.
The state in etcd is being dumped using the following command:
kubectl -n voltha exec $(kubectl -n voltha get pods -lapp=etcd -o=name) -- sh -c "ETCDCTL_API=3 etcdctl get --prefix service/voltha"
- blocks
-
-
- Resolved
-
