Bug 2277200

Summary:	[RFE]: Include FQDN and port in manifest refresh failure messages on WebUI
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.13.6	CC:	aruzicka, bbuckingham
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17:29:41 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 Taft Sanders 2024-04-25 17:01:47 UTC

Description of problem:
A request has been made to include the FQDN and port of the server the Satellite is attempting to connect with during a manifest refresh in any error notifications due to a failure to refresh the manifest.

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

How reproducible:
n/a

Steps to Reproduce:
1.
2.
3.

Actual results:
Error notification message currently indicates a failure in the refresh

Expected results:
Error notification should indicate the FQDN and port used in the manifest refresh along with the error output for the failure.

Additional info:

Comment 1 Eric Helms 2024-06-06 17:29:41 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.