Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1625263

Summary:	Discovery rules with same priority are no longer allowed [QA/Doc only]
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	Discovery Plugin	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Jitendra Yejare <jyejare>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	jyejare, lzap, rabajaj, spetrosi
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	https://projects.theforeman.org/issues/9028
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	Starting with Satellite 6.4, two discovery rules in the same organization cannot have the same priority number. This was causing unexpected results previously. After the upgrade, discovery rules are prioritized according to the discovery framework.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 18:52:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Zapletal 2018-09-04 13:55:19 UTC

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.

Comment 2 Lukas Zapletal 2018-09-04 13:58:39 UTC

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.

Comment 4 Jitendra Yejare 2018-09-05 09:32:33 UTC

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.

Comment 5 Bryan Kearney 2018-10-16 18:52:11 UTC

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