Improper provisioning of analytics_*_ttl values in contrail-analytics-api.conf
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Raj Reddy | |||
R2.20.x |
Won't Fix
|
High
|
Raj Reddy | |||
R2.21.x |
Fix Committed
|
High
|
Raj Reddy | |||
Trunk |
Fix Committed
|
High
|
Raj Reddy |
Bug Description
1) By default, the following options in contrail-
analytics_data_ttl
analytics_
analytics_
analytics_flow_ttl
This overrides the default values of analytics_*_ttl set and therefore the purge operation doesn't take the ttl values into consideration while calculating the purge_cutoff
2) Presently, the default values for analytics_*_ttl options are not same in contrail-
contrail-collector:
-------------------
analytics_data_ttl = 48
analytics_
analytics_
analytics_flow_ttl = 2
contrail-
-------
analytics_data_ttl = 48,
analytics_
analytics_
analytics_flow_ttl = -1,
If the user wants to change the analytics_*_ttl values, then he/she needs to duplicate the ttl values in contrail-
Therefore, we should restrict the ttl configuration to contrail-
no longer affects: | juniperopenstack/r3.0 |
description: | updated |
description: | updated |
Review in progress for https:/ /review. opencontrail. org/14574
Submitter: Raj Reddy (<email address hidden>)