-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
High
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.11
-
Component/s: bbsim
-
Labels:
-
Story Points:1
-
Epic Link:
- - Bring up voltha infra and voltha stack e.g. ATT workflow
- - Bring up BBSIM with helm flags EXTRA_HELM_FLAGS=" --set onu=2,pon=2,controlledActivation=only-onu "
- - Create OLT: voltctl device create -t openolt -H bbsim0.voltha.svc:50060
- - Enable OLT: voltctl device enable <olt-device-id>
- - You will see, no onu will come up!
- - Bring up ONU: kubectl get pods -n voltha | grep bbsim0 | awk 'NR==1{print $1}' followed by kubectl exec -i <bbsim-pod-name> -n voltha – bbsimctl onu poweron BBSM000a0001
- - ONU will reach omci-flows-pushed
- - Disable OLT: voltctl device disable <olt-device-id>
- - Delete OLT: voltctl device delete <olt-device-id>
- - Check voltctl device list is empty
- - Create OLT again: voltctl device create -t openolt -H bbsim0.voltha.svc:50060
- - Enable OLT again: voltctl device enable <olt-device-id>
- - After a short time (I think 5s) 4 ONUs will apear automatically and reach omci-flows-pushed
This is the issue! No ONU should established automatically here because of controlledActivation=only-onu !!!
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 32869,1 | Revert "[VOL-4751] BBSim Wrong handling of controlledActivation=only-onu" | master | bbsim | Status: ABANDONED | 0 | 0 |
| 33060,1 | [VOL-4751] BBSim Wrong handling of controlledActivation=only-onu | master | bbsim | Status: MERGED | +2 | +1 |