Bug 2039764

Summary:	Inconsistency on documented firewall ports
Product:	Red Hat Satellite	Reporter:	Marko Myllynen <myllynen>
Component:	Documentation	Assignee:	Brian Angelica <bangelic>
Documentation sub component:	default	QA Contact:
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	bangelic, ekohlvan, mdolezel
Version:	6.10.2	Flags:	mdolezel: needinfo? (bangelic)
Target Milestone:	Unspecified
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:	2023-06-13 00:19: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 Marko Myllynen 2022-01-12 11:52:55 UTC

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/installing_satellite_server_from_a_connected_network/index#satellite-ports-and-firewalls-requirements_satellite

Section Number and Name: 
1.6. Ports and Firewalls Requirements

Describe the issue: 
Table 1.3 and Table 1.4 listing ports mentions 5646 for katello-agent but the example in Section 1.7 uses 5647.

I think it would also be a good idea to separate deprecated functionality into separate tables, such as katello-agent which will be removed in the future, to make it clearer what is needed if following latest recommendations. Thanks.

Suggestions for improvement: 
Make sure correct port numbers are used.

Comment 1 Marie Hornickova 2022-01-12 16:50:09 UTC

Hi Marko,

Thank you for reporting the issue.  The ticket has been assigned.
We'll prioritize it based on our current workloads and resolve it at the earliest possible.
All updates will be shared here.

Thank you!

Comment 3 Brad Buckingham 2023-05-08 12:50:26 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 4 Brad Buckingham 2023-06-13 00:19:41 UTC

Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 5 Ewoud Kohl van Wijngaarden 2023-08-03 13:40:51 UTC

A bit late, but this came up. Copying https://github.com/theforeman/foreman-documentation/pull/2324#pullrequestreview-1558570565 for completeness.

The QPid router hub port is 4646. So what you have is:

On Server:

* On port 5646 the QPid hub listens for QPid routers
* On port 5647 the QPid router listens for QPid agents (in our case katello-agent)

On Proxy:

* On port 5647 the QPid router listens for QPid agents (in our case katello-agent)
* The QPid router connects to the Server