-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v2.10
-
Component/s: openolt-adapter, openolt-agent
-
Labels:
-
Story Points:2
-
Epic Link:
-
Sprint:VOLTHA 2.10 - Sprint 5
Missing PIR field in TrafficShapingInfo for TCONT Type 1 results in TCONT creation failure at openolt agent.
The following is the bw profile
{
"id" : "TCONT_TYPE1_200Mbps_Fixed_ForVOIP",
"eir" : 0,
"ebs" : 0,
"cir" : 0,
"cbs" : 0,
"air" : 200000
}
These can be represented in meters in one of the following two ways
DefaultMeter{device=of:0000b86a974385f7, cellId=3, appId=DefaultApplicationId{id=177, name=org.opencord.olt}, unit=KB_PER_SEC, isBurst=true, state=ADDED, bands=[DefaultBand{rate=200000, burst-size=0, type=DROP, drop-precedence=null}], annotations={}}
DefaultMeter{device=of:0000b86a974385f7, cellId=3, appId=DefaultApplicationId{id=179, name=org.opencord.olt}, unit=KB_PER_SEC, isBurst=true, state=ADDED, bands=[DefaultBand{rate=200000, burst-size=0, type=DROP, drop-precedence=null}, DefaultBand{rate=200000, burst-size=0, type=DROP, drop-precedence=null}], annotations={}}
When represented the first way, the adapter is not filling the PIR (=GIR) value and this results in openolt-agent complaining that PIR field is missing and results in TCONT creation failure.
It seems like some recent ONOS image change has resulted in meter representation for TCONT Type BW Profile to move aways from two Band representation to single Band representation for Tcont Type 1 profiles exposing this problem.