Bug 1159236 - Wrong System Currency Weights/Multipliers
Summary: Wrong System Currency Weights/Multipliers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Getting Started Guide
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Macpherson
QA Contact: Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks: sat-docs
TreeView+ depends on / blocked
 
Reported: 2014-10-31 09:40 UTC by Tomas Lestach
Modified: 2015-09-16 01:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-16 01:56:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Lestach 2014-10-31 09:40:54 UTC
Description of problem:
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.6/html-single/Getting_Started_Guide/index.html

4.2.1.9. Configuring System Currency Weights/Multipliers

says:
sc.crit = 32
sc.imp = 16
sc.mod = 8
sc.low = 4
sc.bug = 2
sc.enh = 1

Where the parameters are:
sc.crit - multiplier for critical security errata
sc.imp - multiplier for important security errata
sc-mod - multiplier for security errata of moderate importance
sc-low - multiplier for security errata of low importance
sc.bug - multiplier for bugfix errata
sc-enh - multiplier for enhancement errata
...

This is wrong.
For Sat5.6 we use:

# default values for system currency multipliers
# needed by spacewalk-report for system currency report

# multiplier for critical security errata
java.sc_crit = 32

# multiplier for important security errata
java.sc_imp = 16

# multiplier for moderate important security errata
java.sc_mod = 8

# multiplier for low important security errata
java.sc_low = 4

# multiplier for bugfix errra
java.sc_bug = 2

# multiplier for ehnancement errata
java.sc_enh = 1


Note:
* the 'java.' prefix
* current documentation inconsistency in naming (dot vs. dash) - sc.imp sc-mod


Additional Info:
Same parameters will be used for Sat5.7.

Comment 1 Dan Macpherson 2014-11-05 05:41:03 UTC
This appears to be fixed in Satellite 5.7. Will brew the new version of the documentation for verification.

Comment 3 Dan Macpherson 2015-09-16 01:56:15 UTC
This fix has been published in the docs. Closing this bug.


Note You need to log in before you can comment on or make changes to this bug.