Bug 2167371

Summary: "Host - compare content hosts packages" report template should restrict or notify if Host 1* and Host 2* name are same
Product: Red Hat Satellite Reporter: Sneha Arya <snarya>
Component: ReportingAssignee: Ashish Humbe <ahumbe>
Status: CLOSED ERRATA QA Contact: Lucy Fu <lufu>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.13.0CC: ahumbe, lufu, pcreech, rlavi
Target Milestone: 6.14.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-3.7.0.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:18:30 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 Sneha Arya 2023-02-06 12:21:18 UTC
Description of problem:
 
While generating the "Host - compare content hosts packages" report template, It is required to put Host 1* and Host 2* names to compare the packages. However if mistakenly mention the same hostname in both the Host1* and Host2* fields, it allows submitting the request but the error is misleading i.e
 
Error -
At least one of the hosts couldn't be found
 
Version-Release number of selected component (if applicable):
Satellite 6.13
 
How reproducible:
Always
 
Steps to Reproduce:
1. Login to the Satellite 6.13 WebUI
2. Register a client with the satellite e.g "client.example.com"
3. Generate a "Host - compare content hosts packages" report template as follows:
 
Monitor > Report Templates > "Host - compare content hosts packages" > Click on Generate
 
a) Now fill up the field Generate at (Select the date/time)
b) Choose Output format (CVS)
c) Put the Host1* and Host2* value same as "client.example.com"
 
Actual results:
 
Error -
At least one of the hosts couldn't be found
 
Expected results:
 
It should notify or validate the hostname before hitting on submit it. Else can change the misleading error that the host1 and host2 names are the same.

Comment 1 Bryan Kearney 2023-06-02 20:02:49 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36244 has been resolved.

Comment 8 errata-xmlrpc 2023-11-08 14:18:30 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.14 security and bug fix update), 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-2023:6818