if you re-run the compliance job, remediation should not be disabled if the first rule passes. you are trying to remediate based on the latest job run that shows the file system exists ?
why do you need two rules here? why not a if file system exists then check of package is installed ?
Thank you for responding!
Yes I mean that on a complete rerun of the discovery and compliance it will not work unless I delete the component. It seemed like a bug to me. I tested with some much simpler rules to verify that 'disable all remediation' seems to unexpectedly affect future compliance job runs. I am on 8.3.
I tried using a single rule as a workaround, like you suggested, to only check the package if the filesystem exists. But the problem is that then the rule will "pass" if the filesystem is not there (since it won't check the package rule at all), and the person who ran the job saw that it was successful but the package was not installed.
did you open a support ticket about this ? what version of 8.3 ?
Thank you for remembering me.
We are on version 8.3.02.332
I didn't open a ticket as I was hoping it wasn't a bug. Do you think that would be productive? Reproducing it won't be trivial, and we are planning to upgrade to 8.7 by the end of the year.