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 1601499 - Priority uniqueness of the discovery rule should only apply to the current organization
Summary: Priority uniqueness of the discovery rule should only apply to the current or...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Rahul Bajaj
QA Contact: Roman Plevka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-16 13:54 UTC by Roman Plevka
Modified: 2020-02-03 17:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-03 17:42:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24236 0 Normal Ready For Testing priority uniqueness of the discovery rule should only apply to the current organization 2020-02-03 16:40:01 UTC

Description Roman Plevka 2018-07-16 13:54:15 UTC 
there's currently a 1:1 relation between a dsicovery rule and its priority (meaning that a single priority can only be used by a single rule). However this rule applies across all the organizations, meaning, that I as an org admin of orgB am limited by the priorities of rules already created by completely different, non-relevant org.

It would be much more intuitive if each org had discovery rules priorities starting at 0.
Comment 1 Roman Plevka 2018-07-16 13:54:18 UTC 
Created from redmine issue http://projects.theforeman.org/issues/24236
Note You need to log in before you can comment on or make changes to this bug.