dnf-automatic_apply_updates rules in fail after Ansible remedation about content HOT 1 CLOSED

So, I have checked the remediation, OVAL and test scenarios for this rule. I also did some manual tests with the Ansible Playbook and didn't find any issue.

This remediation was recently enabled for RHEL 9 in 5210a71

I found some logs from relevant tests executed about 3 weeks ago, when the remediation was enabled for RHEL9 and this issue was filed. I observed that the dnf-automatic_apply_updates and dnf-automatic_apply_updates rules were failing with many other profiles and not only with anssi_bp28_high.

When investigating the Playbook logs I noticed the dnf-automatic package was installed by package_dnf-automatic_installed but, by any reason that I couldn't figure out, the tasks related to remediation in dnf-automatic_apply_updates and dnf-automatic_apply_updates were not even part of the Playbook.
Since the tasks were not executed, the automatic.conf file was not remediated and the default settings were not compliant. Therefore, the check failure was correct.

Surprisingly, checking the most recent tests I can see the Playbook includes these tasks, proper remediate the system and the check pass after remediation. So, for now this issue is no longer present.

I believe these issues manifested only in a very short period of time while the Ansible remediation was enabled and the tests were executed. Maybe it was just an unfortunate issue of synchronization. I am not sure, but the issue seems no longer valid.

I am closing this and the #11773

from content.