Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2026619

Summary:	[RHOSP16][DOC] Preparing a Satellite server for container images - Satellite's registry doesn't listen at 5000/tcp
Product:	Red Hat OpenStack	Reporter:	Rafal Szmigiel <rszmigie>
Component:	documentation	Assignee:	fallen
Status:	CLOSED CURRENTRELEASE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	amcleod
Target Milestone:	---
Target Release:	---
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:	2022-04-28 15:01:53 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 Rafal Szmigiel 2021-11-25 10:37:37 UTC

Description of problem:

Following the document available at:
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/director_installation_and_usage/index#preparing-a-satellite-server-for-container-images

I found that Satellite's (6.10) container image registry doesn't listen at 5000 but at 443/tcp:

$ podman pull satellite.local:5000/default_organization-osp_containers-swift-container:16.1.6
Trying to pull satellite.local:5000/default_organization-osp_containers-swift-container:16.1.6...
  Get https://satellite.local:5000/v2/: dial tcp 192.168.1.10:5000: connect: connection refused
Error: error pulling image "satellite.local:5000/default_organization-osp_containers-swift-container:16.1.6": unable to pull satellite.local:5000/default_organization-osp_containers-swift-container:16.1.6: unable to pull image: Error initializing source docker://satellite.local:5000/default_organization-osp_containers-swift-container:16.1.6: error pinging docker registry satellite.local:5000: Get https://satellite.local:5000/v2/: dial tcp 192.168.1.10:5000: connect: connection refused

$ podman pull satellite.local/default_organization-osp_containers-swift-container:16.1.6
Trying to pull satellite.local/default_organization-osp_containers-swift-container:16.1.6...
Getting image source signatures
Copying blob a2070ce838f3 done
Copying blob c30189fd3718 done
Copying blob 2cae32376095 done
Copying blob b56859dc70a4 done
Copying blob 17cb0a75ad3b done
Copying blob 8286c6351ee9 done
Copying config deab914c12 done
Writing manifest to image destination
Storing signatures
deab914c128ee6babfcad9e3e7638bfc42d971d40621160633a8e18cf4b57d7c


[root@satellite610 ~]# ss -nlpt | grep 5000
[root@satellite610 ~]#



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

How reproducible:
All the time


Actual results:
Setting port 5000/tcp in containers-prepare-parameter.yaml makes undercloud deployment to fail since Satellite's container image registry does not listen at 5000/tcp.

Expected results:
Deployment of undercloud succeeds. 


Additional info:
Applies to Satellite 6.10 - I didn't test earlier versions.

Comment 2 fallen 2022-04-28 15:01:53 UTC

Merged and published.