The File Integrity Operator uses AIDE to detect changes on node filesystems. In doing this, it configures AIDE according to the user's need.

Up to this point, the AIDE configuration that FIO uses has been relatively stable. New versions of AIDE (specific 0.18.4) are backwards incompatible with the configuration that FIO was using for AIDE.

This results in the AIDE pods falling into a crashloop because AIDE refuses to start with a bad configuration if you're using AIDE 0.18.0+.

Always, so long as your using a container image with AIDE 0.18.0

1. Build the aide container image using the latest available aide (fedora-minimal)
2. Run the e2e tests

You'll notice that the tests timeout, or that File Integrities fail to go to Active phase because AIDE refuses to start with a bad configuration.

The tests should work using newer AIDE versions