filebeat blocked due to filebeat service not running

[kaskavel]

Solutions QA team has a run where, when trying to deploy charmed-kubernetes 1.24 on AWS on focal, the filebeat charm for one of the kubernetes workers remained block with the message: filebeat service not running.

The failure can be seen within this test layer: https://oil-jenkins.canonical.com/job/fce_build_layer/2475//console

The whole test run:
https://solutions.qa.canonical.com/testruns/f534bfad-6d2f-437e-bab8-fc1a78e65527
Logs at the bottom of the page (available with a retention of two weeks).