-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
-
False
-
-
When installing a Red Hat Satellite 6.18 with IoP enabled or upgrading a 6.17 IoP-enabled satellite to 6.18, the installer execution may fail to complete with the following error:
025-11-06 07:53:00 [ERROR ] [configure] Systemd start for iop-core-gateway failed! 2025-11-06 07:53:00 [ERROR ] [configure] journalctl log for iop-core-gateway: 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:52:11 sat618.fqdn systemd[1]: Starting IOP Core Gateway Container... 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:52:12 sat618.fqdn iop-core-gateway[173389]: Trying to pull registry.redhat.io/satellite/iop-gateway-rhel9:6.18... 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:52:12 sat618.fqdn iop-core-gateway[173389]: Pulling image //registry.redhat.io/satellite/iop-gateway-rhel9:6.18 inside systemd: setting pull timeout to 5m0s 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn iop-core-gateway[173389]: Error: initializing source docker://registry.redhat.io/satellite/iop-gateway-rhel9:6.18: reading manifest 6.18 in registry.redhat.io/satellite/iop-gateway-rhel9: received unexpected HTTP status: 502 Bad Gateway 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn podman[173389]: 2025-11-06 07:53:00.148528055 +0100 CET m=+48.242403546 image pull-error registry.redhat.io/satellite/iop-gateway-rhel9:6.18 initializing source docker://registry.redhat.io/satellite/iop-gateway-rhel9:6.18: reading manifest 6.18 in registry.redhat.io/satellite/iop-gateway-rhel9: received unexpected HTTP status: 502 Bad Gateway 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn systemd[1]: iop-core-gateway.service: Main process exited, code=exited, status=125/n/a 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn systemd[1]: iop-core-gateway.service: Failed with result 'exit-code'. 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn systemd[1]: Failed to start IOP Core Gateway Container. 2025-11-06 07:53:00 [ERROR ] [configure] /Stage[main]/Iop::Core_gateway/Podman::Quadlet[iop-core-gateway]/Service[iop-core-gateway]/ensure: change from 'stopped' to 'running' failed: Systemd start for iop-core-gateway failed! 2025-11-06 07:53:00 [ERROR ] [configure] journalctl log for iop-core-gateway: 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:52:11 sat618.fqdn systemd[1]: Starting IOP Core Gateway Container... 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:52:12 sat618.fqdn iop-core-gateway[173389]: Trying to pull registry.redhat.io/satellite/iop-gateway-rhel9:6.18... 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:52:12 sat618.fqdn iop-core-gateway[173389]: Pulling image //registry.redhat.io/satellite/iop-gateway-rhel9:6.18 inside systemd: setting pull timeout to 5m0s 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn iop-core-gateway[173389]: Error: initializing source docker://registry.redhat.io/satellite/iop-gateway-rhel9:6.18: reading manifest 6.18 in registry.redhat.io/satellite/iop-gateway-rhel9: received unexpected HTTP status: 502 Bad Gateway 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn podman[173389]: 2025-11-06 07:53:00.148528055 +0100 CET m=+48.242403546 image pull-error registry.redhat.io/satellite/iop-gateway-rhel9:6.18 initializing source docker://registry.redhat.io/satellite/iop-gateway-rhel9:6.18: reading manifest 6.18 in registry.redhat.io/satellite/iop-gateway-rhel9: received unexpected HTTP status: 502 Bad Gateway 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn systemd[1]: iop-core-gateway.service: Main process exited, code=exited, status=125/n/a 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn systemd[1]: iop-core-gateway.service: Failed with result 'exit-code'. 2025-11-06 07:53:00 [ERROR ] [configure] Nov 06 07:53:00 sat618.fqdn systemd[1]: Failed to start IOP Core Gateway Container.
A usual re-execution of the satellite-installer expected to allow ( and even allows ) the installation or upgrade to complete successfully, but also hints towards some race conditions happening in the registry backend, resulting in the 502 errors.