-
Type: Bug
-
Status: Closed (View Workflow)
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 1.8.0, 1.9.0
-
Fix Version/s: 1.8.0
-
Component/s: None
-
Labels:
-
Environment:
commit 382243012ac88b3682e1267d34d8567e48596bc2
-
Story Points:3
-
Epic Link:
-
Sprint:Junco Sprint #1 - Platform, Junco Sprint #2 - Platform
We noticed some failures in intent install/withdraw latency test when FlowObjective intent compiler is activated. Some intents stuck in INSTALLING state when using "push-test-intents" with a large batch size. This problem can be reproduced after gerrit change 10673.
Steps for replication:
1) Start single-node onos with "drivers, null"
2) Configurations:
cfg set org.onosproject.provider.nil.NullProviders deviceCount 7 cfg set org.onosproject.provider.nil.NullProviders topoShape linear cfg set org.onosproject.provider.nil.NullProviders enabled true cfg set org.onosproject.net.intent.impl.IntentManager skipReleaseResourcesOnWithdrawal true cfg set org.onosproject.net.intent.impl.compiler.IntentConfigurableRegistrator useFlowObjectives true
3) Repeat the following CLI commands
onos> push-test-intents -i null:0000000000000001/6 null:0000000000000007/5 1000 1 Failure: 2 intents not installed onos> push-test-intents -w null:0000000000000001/6 null:0000000000000007/5 1000 1 Time to withdraw 1000 intents: 1458 ms onos> purge-intents