In my environment, Fixlet 200 is not accessible to any of my systems. Unable to create baselines to patch servers. How would I create the baselines for patching these systems.
You havenât said what your issue is?
One thing Iâd point out is that the âimport GPG keyâ should be run first, separately from the baseline. The âprefetchâ commands from the patches, that run before the Action executes, will depend on the GPG keys already being set up.
You also donât say whether youâre using the RHSM plugin, are you using that and if so have you configured the system entitlement certificate?
Iâm receiving content. BigFix is populated with RHEL 8 patches. I have ran the gpg-key for rhel 8 on test system. the task to Delete RHEL 8 Package is not applicable to any of my systems which is preventing me from crea
ting baselines. individually, patches can be applied
Yeah, reading that page, I see how this is not clear.
For a Red Hat 8 Multi-Package Baseline deployment, your Baseline should start with these tasks. These set the client up to begin a multi-package install. It doesnât matter whether Task 200 is relevant, thatâs just meant to clean up after any prior run of a multi-package baseline.
Fixlet ID
Task
200
Delete RHEL 8 Package List File for Multiple-Package Baseline Installation
During the baseline execution, you may observe a âfailedâ status for each of the RPM packages, that changes to Fixed after that last component Task 101 completes. This is because instead of executing each RPM during the baseline component run, all itâs doing is resolving and downloading all of the RPM package dependencies and queuing all of the RPMs for later installation. Then, that last component Task 101 actually executes the RPM / DNF commands to install all of the queued RPMs at once.
That all sounds complicated, but itâs a lot faster & more efficient than running each patch fixlet separately. Without a Multi-Package Installation Baseline, each Fixlet has to download the RPM repo metadata separately to do dependency resolution; with a Multi-Package Baseline, that repo metadata is only downloaded once and then reused for each component action.
Thank you for your help. I was able to complete a baseline with your. The baseline was adjusted to include Fixlet IDâs 200, 300 and 201. 101 was placed at the end of the baseline. I applied 301 to the client outside the baseline, since its only needed once. I had to modify the 200 because its initial relevance 2 to true since it was not picking up RHEL 8 servers in my environment.
This was removed âexist file ((if(exist property âstorage folderâ) then pathname of storage folder of client else pathname of client folder of current site & â/âŚ/âŚâ) & â/EDRDeployData/MultiPkgInstall.txtâ)â andchnged to true.
Baseline were completed successfully after this change was made.
You shouldnât need to force Task 200 to be True though; if itâs false, that just means a previous multi-package baseline has not been run, so no cleanup is needed, and this task would just get skipped when you deploy the baseline
I did and the results were that the task did not hve any relevance on any system. when it was edited and I removed the questionable relevance and ran it, the baselines executed without any problems
Ok, well, if 200 is not relevant it doesnât need to run on the system, that task would just get skipped when itâs part of a baseline but itâs not relevant. No harm in forcing it to run though that I can see.