Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- pre-merge-tested
- qe_fix_request

Blocked:
False
Blocked Reason:
None
Ready:
False
Intelligence Requested:
Market:

Sprint:
NetObserv - Sprint 234
Severity:
Critical

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

When connection tracking is enabled, loki ingestion alert is observed due to drop in flows.
FLP pods show error:

time=2023-04-03T16:52:28Z level=info component=client error=server returned HTTP status 400 Bad Request (400): entry for stream '{DstK8S_Namespace="netobserv", DstK8S_OwnerName="lokistack-gateway", SrcK8S_Namespace="netobserv", SrcK8S_OwnerName="flowlogs-pipeline", _RecordType="newConnection", app="netobserv-flowcollector"}' has timestamp too old: 1677-09-21T00:12:43Z, oldest acceptable timestamp is: 2023-03-27T16:52:28Z fields.level=error fields.msg=final error sending batch host=lokistack-gateway-http.netobserv.svc.cluster.local:8080 module=export/loki status=40062time=2023-04-03T16:52:32Z level=debug msg=ticker signal: invoking action with 775 entries component=utils.Batcher

Observed on a 4.10, .13 cluster with the latest rc operator image. Using 1x.small size lokistack with 3 master and 3 worked with no load running