Unix - File Discovery probe's script.sh parameter appears as a skipped customisation, and reverting to OOTB leaves the script empty - Known Error

Unix - File Discovery probe's script.sh parameter appears as a skipped customisation, and reverting to OOTB leaves the script empty Description Unix - File Discovery probe's script.sh parameter appears as a skipped customization, and reverting to OOTB leaves the script empty.

This appears to be a Default update set customisation by the "admin" user, but it is actually OOTB code doing the customisation, for the purpose of tailoring the shell script for the current instance settings for File Based Discovery.

The problem is that reverting this to OOTB, as is the best practice for all skipped upgrades of OOTB records, and often the first step when debugging Discovery issues, would cause the script to be cleared, breaking File Based Discovery.

Steps to Reproduce

Install File Based Discovery Immediately after install, inspect the Unix - File Discovery probe's script.sh parameter /discovery_probe_parameter.do?sys_id=1bb82a74232313002b6ca45fc7bf65a5 "Value" is empty. This out-of-box version is empty. From the Discovery Console, Enable File-Based Discovery, and Scan SWID Tags for linux. activate and run the cds_client_schedule_list records for samp_file_name, samp_file_set, samp_file_map to synch from CDS. check they all have updated timestamps. Run scheduled job "Discovery - File Discovery Whitelist Update Notification" inspect the Unix - File Discovery probe's script.sh parameter again /discovery_probe_parameter.do?sys_id=1bb82a74232313002b6ca45fc7bf65a5 It now has a script. But is also now has sys_update_xml and sys_update_version records tracking this as a customisation. Check the versions, and this appears to be a Default update set customisation by the "admin" user, but it is actually OOTB code doing the customisation. Upgrade the instance, and this will be listed in the Skipped upgrades to review and revert. revert it to the OOTB version, as is documented best practice for upgrades Run Discovery, and it will fail to run this probe properly. Expected behaviour: Only actual customer customisations should cause skipped upgrades.

Actual behaviour: Confusion and delay is caused during upgrades or debugging, when the probe appears to be customised, and fixing by reverting to OOTB actually breaks it.

Workaround Please do not revert this record back during upgrade, or even if it gets reverted back, on next run on scheduled job (daily run), it will come back to the state which is expected to be.