Adding nodes in IBM Power clusters can result in failed File Integrity node status

Issue

When using the File Integrity Operator on IBM Power systems, you may observe Failed File Integrity node status for newly added nodes when scaling up the cluster.

This issue will manifest after scaling up the machine set. When the new node reaches a Provisioned and Running state, the File Integrity Operator will deploy AIDE to monitor the file system. At this point, any changes to the file system not explicitly excluded in the AIDE configuration file, will result in an alert and Failed node status:

$ oc get fileintegritynodestatuses.fileintegrity.openshift.io
NAME                           NODE          STATUS
example-fileintegrity-worker   worker-node   Failed