With RHN Classic and SAM, Why Does Server and Client Compliance Reporting Disagree?
Updated
Why does the server and client compliance report disagree?
With the 2013 Packaging Model, it is possible to have both new and old SKUs on an account. When this happens, SAM will report a different result than RHN.
This happens because older versions of SAM and RHN now have slightly different ways of calculating compliance.
How do we bring reporting into agreement?
If this situation occurs, you need to update the client applications to reflect the new Model. When it is impractical or not possible to update the client tools, the local reporting should be considered correct.
The minimum version level for Subscription Asset Manager (SAM) is 1.2.
In most cases, simply updating subscription-manager will be enough:
# yum update subscription-manager
However, please review How to use updated subscription-management client tools on older versions of Red Hat Enterprise Linux for dependency notes on some older revisions of Red Hat Enterprise Linux.
Category
Components
Tags
Article Type