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.

Description of problem:
apidoc says the dsicovery_rule is an optional parameter:

discovery_rule[priority]
optional , nil allowed

-however, foreman automatically puts 0 as a priority which causes conflicts on multiple POST requests with no priority specified.

I think it would be nice if foreman automatically chose (or suggested for UI dialog) the next available priority.


Version-Release number of selected component (if applicable):
satellite-6.4.0-10.beta.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Attempt to create two discovery rules with not specifying priority via API
   (there is a screencast in the PR: https://github.com/theforeman/foreman_discovery/pull/445)


Additional info:
Initially reported as issue in Robottelo: https://github.com/SatelliteQE/robottelo/issues/6124

Upstream bug assigned to mhulan

Upstream bug assigned to mhulan

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24235 has been resolved.

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

When you create a new CustomResourceDefinition (CRD), the Kubernetes API Server creates a new RESTful resource path for each version you specify. The CRD can be either namespaced or cluster-scoped, as specified in the CRD's scope field. As with existing built-in objects, deleting a namespace deletes all custom objects in that namespace. CustomResourceDefinitions themselves are non-namespaced and are available to all namespaces. by https://mrtvapk.com/