[Flaky Test] pull-gardener-extension-shoot-rsyslog-relp-e2e-kind fails due to rsyslog
not getting configured properly
#197
Labels
area/testing
Testing related
kind/flake
Tracking or fixing a flaky test
priority/3
Priority (lower number equals higher priority)
How to categorize this issue?
/area testing
/kind flake
Which test(s)/suite(s) are flaking:
pull-gardener-extension-shoot-rsyslog-relp-e2e-kind
CI link:
https://prow.gardener.cloud/view/gs/gardener-prow/pr-logs/pull/gardener_gardener-extension-shoot-rsyslog-relp/193/pull-gardener-extension-shoot-rsyslog-relp-e2e-kind/1854625576917143552
Reason for failure:
Checking whether
rsyslog
is properly started and configured on the shoot's nodes failed with:The tests check if the
rsyslog
service is properly configured by checking if the/etc/rsyslog.d/60-audit.conf
file exists and thersyslog
service is started:gardener-extension-shoot-rsyslog-relp/test/common/verifier.go
Lines 112 to 115 in b39d25b
This file is created by a the configure-rsyslog.tpl.sh script only if the
rsyslog
service is installed on the node.This installation of the
rsyslog
service is done by the following code:gardener-extension-shoot-rsyslog-relp/test/e2e/create_enable_force_delete.go
Lines 38 to 41 in b39d25b
According to the node logs,
rsyslog-relp
was installed at2024-11-07 21:19:42
However, the configure-rsyslog.tpl.sh was still detecting it as not installed for a very long time (more than 10 minutes)
Anything else we need to know:
N/A
The text was updated successfully, but these errors were encountered: