6 Replies Latest reply: Jun 28, 2012 1:49 AM by piyush pandey RSS

SuSe Patch Analysis Scenario

piyush pandey

Hi,

I am trying to analyze my server against a kernel-default rpm. My Current system has  2.6.32.36-0.5 installed on it. I was trying to analyze against a lower version (2.6.32.19-0.3.1) but the analysis result showed the missing rpm version as 2.6.32.59-0.3 .

 

Now  I wanted to understand why it showed a RPM missing at the version which is the highest version present in the catalog. It should either show the next hightest version of Current kernel or the white list kernel level as missing and not the highest kernel level in the repository.

2.6.32.19-0.3.1(whitelist rpm  < 2.6.32.36-0.5(current) < 2.6.32.59-0.3 (showed result)

  • 1. SuSe Patch Analysis Scenario
    Lazar NameToUpdate

    Your catalog should only have one versionof any given rpm. When you use the include list, it only checks for that rpm name, not version. So in your casse you are running analysis against kernel-default, so you get the missing rpm of a version which is in your catalog..

  • 2. SuSe Patch Analysis Scenario
    piyush pandey

    Hi,

    But if suppose I have a intermedian Kernel Level like 2.6.32.48-0.5 (this is < than 2.6.32.59-0.3) (higher than Current Kernel Version but not the latest in Repository) how can i get the Intermedian Kernel Level Patch as missing and not the Latest Kernel in Repo in patch analysis.

  • 3. SuSe Patch Analysis Scenario
    Rohit Nayyar

    When u have more than one version of the same rpm/package in your repository, the most latest one is used by BBSA, because yum behaves this way and this is well understood and reasonable.

    When You specify white/black or include/exclude list, the version is not counted in analysis and yum picks the highets version.

    The only way to get a intermediate version will be to have a new repository which has this version as highest, create a catalog based on this repo and an analysis job based on this CUJ.

  • 4. Re: SuSe Patch Analysis Scenario
    Lazar NameToUpdate

    Use this to create custom catalog with your version of the rpm. KB has the details and gotchas:

     

    KA372001 - BBSA Red Hat Linux Patching: How to create a Catalog using custom RPM packages

    https://kb.bmc.com/infocenter/index?page=content&id=KA372001

     

    Though keep in mind that even if you create a custom Catalog with the kernel (or kernel-default or any other rpm for that matter) of lower version than you already have isntalled, the Patch Analysis Job will not find it missing. The intent of patching is to provide you updates, not roll you back to previous versions.

  • 5. Re: SuSe Patch Analysis Scenario
    Bill Robinson

    Can you clarify how your whitelist is setup?  is this a patch smart group?  what rpms are listed in there?

     

    Why do you think it should not show the highest kernel version ?

  • 6. SuSe Patch Analysis Scenario
    piyush pandey

    In Whitelist we used the following name of rpm: kernel-default-2.6.32.48-0.5.x86_64.rpm

    Repository Server Has Highest Version available: kernel-default-2.6.32.59-0.3.1.x86_64.rpm

    Current Kernel Level of Server: kernel-default-2.6.32.36-0.5.x86_64.rpm