Bug #35783
closedThe "pulp_docker_registry_port" settings is still exposed and set to port 5000
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2103424
Description of problem:
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):
Pulp 3 Katello
How reproducible:
Always
Steps to Reproduce:
Either go to Administer --> Settings --> Content and check for "Pulp Docker registry port"
or run this command 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
Updated by The Foreman Bot about 2 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/Katello/katello/pull/10366 added
Updated by Ian Ballou about 2 years ago
- Subject changed from The "pulp_docker_registry_port" settings is still exposed and set to port 5000 to The "pulp_docker_registry_port" settings is still exposed and set to port 5000
- Category set to Container
- Target version set to Katello 4.8.0
- Triaged changed from No to Yes
Updated by The Foreman Bot about 2 years ago
- Fixed in Releases Katello 4.8.0 added
Updated by Anonymous about 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|b31ae26d5ee9ed255c2665780b1968ed53a904b1.