We are facing an issue with the automatic creation of Baseline through the BigFix REST API.
Apparently, one or more Fixlet released recently is causing an error when our automation tries to add them to a baseline. Returning the error A baseline component cannot be filled in from source because the provided source link references content that does not exist.
This error shows up only when we try to add the latest fixlets for office released in the last thirty days, for older fixlets we don’t see this error.
We haven’t been able to determine what has changed so we are looking for any insights from HCL to know if something has changed in the meta-data of the Fixlets during the latest releases, this is stopping our automation to work and causing manual work in order to add the Fixlets to our patching baselines.
(Moved thread to new topic, the other 19 fixlets are in “Patches for Windows”, vs the “Updates for Windows Applications” release announcement on the original topic)
The other 19 fixlets all appear to exist, in “Patches for Windows” (Enterprise Security). They all have Default Actions and the content IDs for the Default Actions are all the same (“Action1”). I don’t see anything other than the two non-existant fixlet IDs that should prevent a Baseline from being created.
That seems to be the caused, somebody in my team created custom copies of a couple of Office Fixlets and they were hidden but the automation was trying to add them to the baseline with the default source references.
I confirm that the automation was picking up custom copies of two fixlets from the Security Enterprise Site and was trying to add them to the baseline using the original source meta-data.
Once I deleted the custom copies and added additional validations the automation was able to generate the Baselines.
