Problem description
Upgrade from 2025.07 to 2025.10 failed with "Error: cannot prepare images: exit status 125"
Steps to reproduce
- Run the following command:
sudo mgradm upgrade podman --logLevel debug --ssl-db-ca-root /root/_.lab.tierpoint.com/gd_bundle-g2.crt --ssl-db-cert /root/_.lab.tierpoint.com/1b64d28f679b948e.crt --ssl-db-key /root/_.lab.tierpoint.com/_.lab.tierpoint.com.decrypted.key
- It fails:
2:50PM INF mgradm/cmd/cmd.go:69 > Starting mgradm upgrade podman --logLevel debug --ssl-db-ca-root /root/_.lab.tierpoint.com/gd_bundle-g2.crt --ssl-db-cert /root/_.lab.tierpoint.com/1b64d28f679b948e.crt --ssl-db-key /root/_.lab.tierpoint.com/_.lab.tierpoint.com.decrypted.key
2:50PM INF mgradm/cmd/cmd.go:70 > Use of this software implies acceptance of the End User License Agreement.
2:50PM DBG shared/utils/exec.go:120 > Running: bash -c
# inspect.sh, generated by mgradm
echo "scc_username=$(cat /etc/zypp/credentials.d/SCCcredentials 2>/dev/null | grep username | cut -d= -f2 || true)"
echo "scc_password=$(cat /etc/zypp/credentials.d/SCCcredentials 2>/dev/null | grep password | cut -d= -f2 || true)"
echo "has_uyuni_server=$(systemctl list-unit-files uyuni-server.service >/dev/null && echo true || echo false)"
echo "has_salt_minion=$(systemctl list-unit-files venv-salt-minion.service >/dev/null && echo true || echo false)"
exit 0
2:50PM INF shared/podman/network.go:32 > Setting up uyuni network
2:50PM DBG shared/podman/network.go:96 > IPv6 is enabled
2:50PM DBG shared/podman/network.go:39 > uyuni network already present
2:50PM DBG shared/utils/exec.go:203 > Running: podman network inspect --format {{.IPv6Enabled}} uyuni
2:50PM INF shared/podman/network.go:50 > Reusing existing uyuni network
⠋ hostname -f
2:50PM INF shared/utils/utils.go:235 > Computed image name is registry.opensuse.org/uyuni/uyuni/server:latest
2:50PM INF shared/utils/utils.go:235 > Computed image name is registry.opensuse.org/uyuni/uyuni/server-postgresql:latest
2:50PM INF shared/podman/images.go:46 > Pull Policy is always. Presence of RPM image will be checked and pulled from registry if not present
2:50PM DBG shared/podman/images.go:171 > Looking for installed RPM package containing registry.opensuse.org/uyuni/uyuni/server:latest image
2:50PM INF shared/podman/images.go:175 > skipping loading image from RPM as /usr/share/suse-docker-images/native/ doesn't exist
2:50PM INF shared/podman/images.go:64 > Cannot find RPM image for registry.opensuse.org/uyuni/uyuni/server:latest
2:50PM DBG shared/podman/images.go:69 > Pulling image registry.opensuse.org/uyuni/uyuni/server:latest because it is missing and pull policy is not 'never'
2:50PM INF shared/podman/images.go:273 > Running podman pull registry.opensuse.org/uyuni/uyuni/server:latest
2:50PM DBG shared/utils/exec.go:186 > Running: podman pull registry.opensuse.org/uyuni/uyuni/server:latest
2:50PM ??? Cmd output > Trying to pull registry.opensuse.org/uyuni/uyuni/server:latest...
2:50PM ??? Cmd output > Error: initializing source docker://registry.opensuse.org/uyuni/uyuni/server:latest: reading manifest latest in registry.opensuse.org/uyuni/uyuni/server: name unknown
2:50PM ERR shared/utils/cmd.go:94 > error="cannot prepare images: exit status 125"
Error: cannot prepare images: exit status 125
Uyuni version
Uyuni version: 2025.07-241000.1.1.uyuni5
Uyuni proxy version (if used)
uyuni-tools version used to deploy/manage the server or proxy (if relevant)
Package: mgradm
Version: 5.2.1-241000.1.1.uyuni5
Priority: optional
Section: System/Management
Maintainer: Uyuni packagers <devel@lists.uyuni-project.org>
Installed-Size: 27.5 MB
Depends: libc6
Homepage: https://github.com/uyuni-project/uyuni-tools
Download-Size: 11.9 MB
APT-Manual-Installed: yes
APT-Sources: http://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable:/ContainerUtils/Ubuntu_24.04 ./ Packages
Description: Command line tool to install and update Uyuni
mgradm is a convenient tool to install and update Uyuni components as containers running
either on Podman or a Kubernetes cluster.
Useful logs
2:55PM INF mgradm/cmd/cmd.go:69 > Starting mgradm upgrade podman --logLevel debug --ssl-db-ca-root /root/_.lab.tierpoint.com/gd_bundle-g2.crt --ssl-db-cert /root/_.lab.tierpoint.com/1b64d28f679b948e.crt --ssl-db-key /root/_.lab.tierpoint.com/_.lab.tierpoint.com.decrypted.key
2:55PM INF mgradm/cmd/cmd.go:70 > Use of this software implies acceptance of the End User License Agreement.
2:55PM DBG shared/utils/exec.go:120 > Running: bash -c
# inspect.sh, generated by mgradm
echo "scc_username=$(cat /etc/zypp/credentials.d/SCCcredentials 2>/dev/null | grep username | cut -d= -f2 || true)"
echo "scc_password=$(cat /etc/zypp/credentials.d/SCCcredentials 2>/dev/null | grep password | cut -d= -f2 || true)"
echo "has_uyuni_server=$(systemctl list-unit-files uyuni-server.service >/dev/null && echo true || echo false)"
echo "has_salt_minion=$(systemctl list-unit-files venv-salt-minion.service >/dev/null && echo true || echo false)"
exit 0
2:55PM INF shared/podman/network.go:32 > Setting up uyuni network
2:55PM DBG shared/podman/network.go:96 > IPv6 is enabled
2:55PM DBG shared/podman/network.go:39 > uyuni network already present
2:55PM DBG shared/utils/exec.go:203 > Running: podman network inspect --format {{.IPv6Enabled}} uyuni
2:55PM INF shared/podman/network.go:50 > Reusing existing uyuni network
2:55PM DBG shared/utils/exec.go:203 > Running: hostname -f
2:55PM INF shared/utils/utils.go:235 > Computed image name is registry.opensuse.org/uyuni/uyuni/server:latest
2:55PM INF shared/utils/utils.go:235 > Computed image name is registry.opensuse.org/uyuni/uyuni/server-postgresql:latest
2:55PM INF shared/podman/images.go:46 > Pull Policy is always. Presence of RPM image will be checked and pulled from registry if not present
2:55PM DBG shared/podman/images.go:171 > Looking for installed RPM package containing registry.opensuse.org/uyuni/uyuni/server:latest image
2:55PM INF shared/podman/images.go:175 > skipping loading image from RPM as /usr/share/suse-docker-images/native/ doesn't exist
2:55PM INF shared/podman/images.go:64 > Cannot find RPM image for registry.opensuse.org/uyuni/uyuni/server:latest
2:55PM DBG shared/podman/images.go:69 > Pulling image registry.opensuse.org/uyuni/uyuni/server:latest because it is missing and pull policy is not 'never'
2:55PM INF shared/podman/images.go:273 > Running podman pull registry.opensuse.org/uyuni/uyuni/server:latest
2:55PM DBG shared/utils/exec.go:186 > Running: podman pull registry.opensuse.org/uyuni/uyuni/server:latest
2:55PM ??? Cmd output > Trying to pull registry.opensuse.org/uyuni/uyuni/server:latest...
2:55PM ??? Cmd output > Error: initializing source docker://registry.opensuse.org/uyuni/uyuni/server:latest: reading manifest latest in registry.opensuse.org/uyuni/uyuni/server: name unknown
2:55PM ERR shared/utils/cmd.go:94 > error="cannot prepare images: exit status 125"
Error: cannot prepare images: exit status 125
Additional information
No response
Problem description
Upgrade from 2025.07 to 2025.10 failed with "Error: cannot prepare images: exit status 125"
Steps to reproduce
sudo mgradm upgrade podman --logLevel debug --ssl-db-ca-root /root/_.lab.tierpoint.com/gd_bundle-g2.crt --ssl-db-cert /root/_.lab.tierpoint.com/1b64d28f679b948e.crt --ssl-db-key /root/_.lab.tierpoint.com/_.lab.tierpoint.com.decrypted.keyUyuni version
Uyuni proxy version (if used)
uyuni-tools version used to deploy/manage the server or proxy (if relevant)
Useful logs
Additional information
No response