Patch Policy - Action not created - getting message on autopatch.log "bf:bfdata-autopatch:mags:error No applicable patches for user:"

Hi,

Patch Policy - Action not created - getting a message on autopatch.log “bf:bfdata-autopatch:mags:error No applicable patches for user:”

After discussion about this issue with the HCL Support, the following information gathered:
Non of the Patches that has been declared on the Patch Policy was relevant, because of that the Patch Policy action not created

I can understand this statement but, from the customer point of view , he does not know what happened.
When you go to the autopatch.log there is only the following line: “bf:bfdata-autopatch:mags:error No applicable patches for user: …” - No indication about the Patch Policy ID or Name, Schedule ID or Name

I think that added a message in the autopatch.log file like:
"bf:bfdata-autopatch:mags:error “Patch Policy Name - Schedule Name - No applicable patches for user:…” will be much helpful and if it can be seen in the Patch Policy WebUI itself

I know that If I enable the debug logging for the BigFix WebUI - I will see in the Log file in the following manner:
2022-11-23T13:40:05.435Z bf:autopatch:engine:debug Time to execute next policy scheduled job. Locking engine for processing schedule job queue.
2022-11-23T13:40:05.435Z bf:autopatch:engine:debug Job to be processed: {“scheduleID”:5,“policyID”:4,“jobID”:55,“jobType”:“ROLLOUT”,“status”:“new”,“triggerTime”:“2022-11-23T13:40:00.000Z”}
2022-11-23T13:40:05.435Z bf:autopatch:engine:debug Rolling out patches for Policy ID 4 Schedule ID 5, with Job ID 55

Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:mags:debug Bucketing computer group list by owner for 1 computers for schedule ID 5

Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:mags:debug Creating MAG for User 1 with preview ID 4 and schedule ID 5

Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:mags:debug Retrieved patchlist with 0 patches to deploy. Getting default actions for those patches.
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:mags:debug Retrieved customPatchlist with 0 patches to deploy. Getting default actions for those patches.
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:patches:debug getPatchDefaultActionByIDs: patchIDList is empty, returning
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:patches:debug getCustomDefaultActionByIDs: customIDList is empty, returning
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:patches:debug getCustomDefaultActionByIDs: customIDList is empty, returning
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:patches:debug getCustomDefaultActionByIDs: customIDList is empty, returning
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:mags:debug Default actions retreived for patchlist. Posting MAGs.
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:mags:error No applicable patches for user: XXXX
2022-11-23T13:40:05.489Z bf:autopatch:engine:debug Job execution completed successfully
2022-11-23T13:40:05.489Z bf:autopatch:engine:debug Setting job status to 'done’
Wed, 23 Nov 2022 13:40:05 GMT bf:bfdata-autopatch:enginejobs:debug Updating status for job ID 55 to done

How do you handle this situation?

Hi or,
Does relevance statement is blocking you from getting the client-id /? (network-security wise)
Did You Try to use the : [Corrupt Fixlet Wizard] ?

https://help.hcltechsw.com/bigfix/9.2/patch/Patch_Man/Patch_Man_Windows/c_fix_corrupt_patches_using_the_.html

I’m using the WebUI Patch Policy , don’t understand how it’s related. please elaborate :slight_smile: