Bug 2006838

Summary: [RFE] add reportig table for duplicate or same values for host facts
Product: Red Hat Satellite Reporter: Stefan Nemeth <snemeth>
Component: ReportingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: dsinglet, jlenz, mhulan
Target Milestone: UnspecifiedKeywords: EasyFix, FutureFeature, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 01:03:52 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 Stefan Nemeth 2021-09-22 14:02:56 UTC
Description of problem:

Satellite 5 used to have feature to list duplicate information in db. For example if someone clones host and does not do it properly you may end up with same uuids on different hosts. 

In some occasions, there can be duplicate mac adresses, IPs, names .. etc


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

6.10
7.0

How reproducible:

100%

Steps to Reproduce:

for example:

1.install rhel server on vmware or rhev
2.clone it without following proper policies
https://access.redhat.com/solutions/198693
3.register to satellite


Actual results:


Expected results:

have option to report duplicate values

Additional info:

Comment 4 Brad Buckingham 2022-11-03 21:48:15 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 8 Leos Stejskal 2023-03-03 09:08:00 UTC
Created redmine issue https://projects.theforeman.org/issues/36159 from this bug

Comment 9 Eric Helms 2024-06-06 01:03:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.