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 2120327 - Discovery Organization setting is shown as Discovery Location setting
Summary: Discovery Organization setting is shown as Discovery Location setting
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Settings
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.12.0
Assignee: Leos Stejskal
QA Contact: Shweta Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-22 14:48 UTC by Griffin Sullivan
Modified: 2022-11-16 13:35 UTC (History)
4 users (show)

Fixed In Version: tfm-rubygem-foreman_discovery-21.0.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:35:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35474 0 Normal New Discovery Organization setting is shown as Discovery Location setting 2022-09-01 13:33:57 UTC
Red Hat Issue Tracker SAT-12488 0 None None None 2022-08-25 15:03:18 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:35:44 UTC

Description Griffin Sullivan 2022-08-22 14:48:24 UTC
Description of problem:
Under Discovery settings, there are two entries for Discovery Location and none for Discovery Organization. One of these entries is actually the Discovery Organization setting but the UI is overriding it as a duplicate Discovery Location setting.

Version-Release number of selected component (if applicable):
6.12 snap 7

How reproducible:
100%

Steps to Reproduce:
1. Go to Settings > Discovery

Actual results:
2 entries for Discovery Location, but one is mapped to organization.

Expected results:
1 entry for location and one entry for organization.

Comment 1 Brad Buckingham 2022-08-25 14:20:20 UTC
Is this a regression from 6.11?

Comment 2 Griffin Sullivan 2022-08-25 14:29:02 UTC
Yes this is a regression.

Comment 3 Leos Stejskal 2022-09-01 13:33:56 UTC
Created redmine issue https://projects.theforeman.org/issues/35474 from this bug

Comment 4 Bryan Kearney 2022-09-01 20:05:23 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35474 has been resolved.

Comment 5 Shweta Singh 2022-09-12 08:53:49 UTC
Verified.

Version Tested: Satellite 6.12 Snap 10.0

Verification Steps:
1. Navigate to Settings->Discovery on UI
2. Verify that no duplication of any setting(like location) should be present and "discovery organization" should be present and can be updated.   

Result: 
"discovery organization" setting is present and can be modified.

Comment 9 errata-xmlrpc 2022-11-16 13:35:34 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 (Important: Satellite 6.12 Release), 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-2022:8506


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