Bug 2103424

Summary:	The "pulp_docker_registry_port" settings is still exposed and set to port 5000 in Satellite 6.11
Product:	Red Hat Satellite	Reporter:	Sayan Das <saydas>
Component:	Container Management - Content	Assignee:	Ian Ballou <iballou>
Status:	CLOSED ERRATA	QA Contact:	Chris Roberts <chrobert>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.11.0	CC:	chrobert, iballou, pcreech
Target Milestone:	6.14.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 14:18:01 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 Sayan Das 2022-07-03 07:01:59 UTC

Description of problem:

After the introduction of Pulp 3 in Satellite 6.10 and above, there is no crane plugin in pulp3 and hence the docker registry is also not exposed via port 5000

However, if we are to go to Administer --> Settings --> Content, We still can see that option available and set.


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

Satellite 6.10 and 6.11


How reproducible:
Always


Steps to Reproduce:
1. Install a Satellite 6.11
2. Either go to Satellite UI --> Administer --> Settings --> Content and check for "Pulp Docker registry port" 

   or run this command in Satellite via hammer:

   # hammer settings info --name pulp_docker_registry_port


Actual results:

# hammer settings info --name pulp_docker_registry_port
Id:            pulp_docker_registry_port
Name:          pulp_docker_registry_port
Description:   The port used by Pulp Crane to provide Docker Registries
Category:      Content
Settings type: integer
Value:         5000



Expected results:

If my assumption is correct, this setting should no longer be present or its Pulp3 alternate should be present there.


Additional info:

I see that in Katello itself it is still defined. 

https://github.com/Katello/katello/blob/master/lib/katello/plugin.rb#L502-L506

Comment 4 Ian Ballou 2022-11-23 21:04:54 UTC

Created redmine issue https://projects.theforeman.org/issues/35783 from this bug

Comment 5 Bryan Kearney 2022-11-24 00:03:10 UTC

Upstream bug assigned to iballou

Comment 6 Bryan Kearney 2022-11-24 00:03:11 UTC

Upstream bug assigned to iballou

Comment 7 Bryan Kearney 2022-12-06 20:03:00 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35783 has been resolved.

Comment 8 Chris Roberts 2023-06-27 16:12:12 UTC

Settings is no longer in the UI or visible with hammer:

[root@sat-6-14-qa-rhel8 ~]# hammer settings list | grep -i docker
ignored_interface_identifiers                          | Ignore interfaces with matching identifier                  | ["lo", "en*v*", "usb*", "vnet*", "macvtap*", ";vdsmdummy;", "veth*", "docker*... | Skip creating or updating host network interfaces objects with identifiers ma...
excluded_facts                                         | Exclude pattern for facts stored in foreman                 | ["lo", "en*v*", "usb*", "vnet*", "macvtap*", ";vdsmdummy;", "veth*", "docker*... | Exclude pattern for all types of imported facts (puppet, ansible, rhsm). Thos...

Comment 11 errata-xmlrpc 2023-11-08 14:18:01 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