It can be useful to manually run yum or blyum with the repodata and includes from the command line to get a better picture of what might be happening during analysis or inspect the repodata or perform any other troubleshooting steps. The following steps can be taken to accomplish this:
For 8.9.01 and below
Run the Patching Job with the DEBUG_MODE_ENABLED set to true.
Gather the per-host generated data from the application server - for example if the Job Name is 'RedHat Analysis' and it was run against the target 'red6-88.example.com' on Jun 11 you should see a directory:
<install dir>/NSH/tmp/debug/application_server/RedHat Analysis/Sat Jun 11 09-26-57 EDT 2016/red6-88.example.com
analysis_err.log analysis_log.log analysis_res.log installed_rpms.log repo repodata.tar.gz yum_analysis.res yum.conf yum.err.log yum.lst
Copy the entire red6-88.example.com directory back to the target system (or any system you want to test these files on) into /tmp or some other location.
For 8.9.01 and later
The files mentioned above are kept in <rscd install>/Transactions/analysis_archive on the target system. The three most recent runs should be present.
Once you've located the files used for analysis and located them on the target system
Edit the yum.conf and the cachedir and reposdir to match the current directory path. Following the pre-8.9.01 example where we copied the directory into /tmp:
are changed to match the new path - if you copied the red6-88.example.com to /tmp then:
then from within that directory you can run:
/opt/bmc/bladelogic/NSH/bin/blyum -c yum.conf -C update
if an include list was used you can do:
/opt/bmc/bladelogic/NSH/bin/blyum -c yum.conf -C update `cat rpm-includes.lst.old`
/opt/bmc/bladelogic/NSH/bin/blyum -c yum.conf -C update `cat parsed-include.lst.old`
if the parsed list exists. The parsed include list will not contain any rpms that are installed on the target and in the include list. The parsed-include.lst was added in recent BSA versions to handle the situation where yum decides to update the rpm to the latest one in the catalog instead of leaving it alone when the include list contains the exact version of an rpm already installed on the system.
If it's a RedHat 7 target, the native yum is used, so use yum instead of blyum.
yum -c yum.conf -C update
You can also use the above process to copy the metadata from the target system to another system and run queries against the metadata or run analysis with the same metadata and options against a test system. for example you could run:
/opt/bmc/bladelogic/NSH/bin/blyum -c yum.conf -C search <rpmname>
/opt/bmc/bladelogic/NSH/bin/blyum -c yum.conf -C info <rpmname>
to see if some rpm is in the metadata or not.