TTL value of analytics_data_ttl is being wrongly considered instead of analytics_config_audit_ttl
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Undecided
|
Raj Reddy | |||
R2.21.x |
Fix Committed
|
Undecided
|
Raj Reddy | |||
R2.22.x |
Fix Committed
|
Undecided
|
Raj Reddy | |||
R3.0 |
Fix Committed
|
Undecided
|
Raj Reddy | |||
Trunk |
Fix Committed
|
Undecided
|
Raj Reddy |
Bug Description
Contrail Build 2.21.1 - Build 22
1. Define below parameters explicitly in contrail-
analytics_
analytics_
analytics_
analytics_
2. Make configuration changes (create/delete virtual-networks) with Web UI once in every hour.
3. Three hours later, check logs with following commands.
a. contrail-logs --object-type config --start-time now-3h --end-time now-1h
b. contrail-logs --object-type config --start-time now-1h --end-time now
The result was, "a." shows nothing and "b." shows logs for last one hour.
So, I guess the TTL value of analytics_data_ttl is being considered here. Per my understanding, the TTL of analytics_
Greetings,
Sandeep.
information type: | Proprietary → Public |
tags: | added: analytics |
Changed in juniperopenstack: | |
assignee: | nobody → Raj Reddy (rajreddy) |
Review in progress for https:/ /review. opencontrail. org/18591
Submitter: Raj Reddy (<email address hidden>)