Red Hat Bugzilla – Bug 1625263
Discovery rules with same priority are no longer allowed [QA/Doc only]
Last modified: 2018-10-16 14:52:11 EDT
Starting from Satellite 6.4, two discovery rules in the same organization are not allowed to have the same priority number. This was leading to unexpected results previously. During upgrade process, rules are sorted out as they are being processed by discovery framework and assigned priority numbers 0, N+100. After the upgrade, priority numbers can be edited as needed. This is just a tracking BZ for Release Note changes and QA awareness.
QA NOTE: If there are existing discovery rules they are sorted out by PRIORITY and if that's missing by CREATION DATE/TIME. Then priority numbers are assigned: 0 100 200 300 400 etc Discovery rule with same priority cannot be entered anymore after the upgrade.
Verified! @ Satellite 6.4 snap 20 Scenario 1: Steps: 1. Discovery rules are created before the upgrade with 0 priority. 2. Upgraded from 6.3 to 6.4 3. Observe the discovery rules priorities. Observation: 1. The discovery rule priorities are set to 100 and 200 according to the discovery framework. 2. The priority is able to change post upgrade. Scenario 2: Steps: 1. Attempt to create discovery rule with priority matching with already existing rule. Observation: The discovery rule is not created with the same priorities. Priority already taken error is displayed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927