IBM Support

Are there any known issues with the "Linux RPM Patching" product?

Technote (troubleshooting)


Problem(Abstract)

The article points out some known issues that are common with the Linux RPM Patching product and processes.

Resolving the problem

  • Some SuSE RPM packages are not downloadable from Novell.com, and they are in the Installation ISOs only.
    Solution: This will be manual process, and ISOExtractor.exe can help to simply this process. See KB 1009 for more information.
  • There are no SuSE pre-packaged fixlets for the user to customize.
    Solution: In current phase, we do not provide pre-packaged SuSE fixlets but we will in the next phase. Currently the multi-Fixlet mode in "Create Custom Fixlet" page is not available for SuSE. User needs to enter full rpm of the SuSE Linux RPM packages.
  • Potential Download Mirroring problem in DSA
    Solution: This should not be a huge problem because during normal operation, each DSA TEM server automatically downloads and caches files from the other. When taking action from Fixlet # 7 "Run Download Cacher Tool - Red Hat Enterprise Linux" or taking action from the custom fixlet that is generated by the "Linux RPM Patching" Dashboard, user can target both DSA TEM Server so that RPM packages will be cached on both Server. The minor drawback is duplication. Another workaround is to run the download cacher manually on bother server with same set of switches/arguments. Alternatively, you can also run the download cacher on one primary TEM Server, and transfer the files over to the secondary TEM Server.
  • How to download RPM package in an Air-Gapped Network?
    Solution: yes, but it will be manual process like the other products. Basically user need to look into TEM Client Log file (Default: C:\Program Files\BigFix Enterprise\BES Client\__BESData\__Global\Logs) to find the command line. Then the user need to run the same command on machine that is connected to the internet for downloading the required RPM Packages. At the end user need to transfer those file back to the sha1 folder of the original TEM Server machine.
    For Red Hat Linux Enterprise, follow the below instructions:
    1. Go the TEM Client Log file folder (See default path above)
    2. Find the RHEL air gap files based on the action ID.
    3. Transfer those two files to the computer that is connected to the internet.
    4. Download the RHEL.UnixSD download cacher and run it based on the arguments listed on the file whose name starts with "RHEL_Airgap".Please note that you might need to change some arguments, such "Cache", and log file directory etc.
    For SuSE Enterprise Linux, follow the below instructions:
    1. Go the TEM Client Log file folder (See default path above)
    2. Find the SuSE air gap files based on the action ID. There may be two files if you are caching rpm package for bother SuSE 9 and SuSE 10 fixlets.
    3. Transfer those two files to the computer that is connected to the internet.
    4. Download the SUSE Download Cacher and run it based on arguments listed on the file(s). Please note that you might need to change some arguments, such "Cache", and log file directory etc.

Historical Number

1072

Document information

More support for: IBM BigFix family

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1505756

Modified date: 05 December 2014


Translate this page: