Skip to content

[iptables] journald input system tests failing #6547

@ebeahan

Description

@ebeahan

iptables.log system integration tests failing to find expected data against stack 8.8 (and all stack versions since 8.1 from testing):

2023/06/12 15:48:10 DEBUG checking for expected data in data stream...
2023/06/12 15:48:10 DEBUG found 0 hits in logs-iptables.log-ep data stream: index_not_found_exception: no such index [logs-iptables.log-ep] Status=404
2023/06/12 15:48:11 DEBUG found 0 hits in logs-iptables.log-ep data stream: index_not_found_exception: no such index [logs-iptables.log-ep] Status=404
2023/06/12 15:48:12 DEBUG found 0 hits in logs-iptables.log-ep data stream: index_not_found_exception: no such index [logs-iptables.log-ep] Status=404
2023/06/12 15:48:13 DEBUG found 0 hits in logs-iptables.log-ep data stream: index_not_found_exception: no such index [logs-iptables.log-ep] Status=404

Suspect whatever underlying problem here also impacts the journald integration package. Past discussion of similar issue #2602 that was resolved by a workaround in #5984.

Metadata

Metadata

Assignees

Labels

Integration:iptablesIptablesbugSomething isn't working, use only for issues

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions