-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
-
Using downstream RHSI, if you are not authenticated (via
podman login registry.redhat.io
) you'll get an error message
Error: Error initializing Skupper - error creating skupper component: skupper-router - error creating container skupper-router: [POST /libpod/containers/create][500] containerCreateLibpodInternalServerError &{Because:image not known Message:registry.redhat.io/service-interconnect/skupper-router-rhel9:2.4.3: image not known ResponseCode:500}
This is related to 1284, where the gateway init will fail (and not recover unless you delete the gateway).
In this case, skupper init works after logging in to the registry without any other action needed.
However, a more "speaking" error message or a mention of this behaviour in the docs would be helpful.
- is related to
-
SKUPPER-1284 podman type skupper gateway doesn't recover from a failed image pull
- Backlog