mgradm support config fails on SUSE Multi-Linux Manager Hub

SUSE Multi-Linux Manager 5.0

When running the mgradm support config command on the SUSE Multi-Linux Manager Hub, the process fails while attempting to inspect the uyuni-hub-xmlrpc container and prepare the tarball. This is indicated by errors related to podman inspect and file access issues.

This issue has been reported to engineering and will be fixed within a future update. Please open a case to request a PTF.

To workaround run supportconfig manually e.g. start terminal session for uyuni server and run supportconfig within container and once for the host:

mgrctr term
uyuni-server:/ # supportconfig
uyuni-server:/ # exit
cp /var/lib/containers/storage/volumes/var-log/_data/scc_*.txz* /path/to/space/
supportconfig

Please provide both supportconfigs.

The mgradm support config command fails due to issues with podman inspect and file access within the uyuni-server container.

suma50hub:~ # mgradm --logLevel trace support config
9:01AM INF mgradm/cmd/cmd.go:66 > Welcome to mgradm
9:01AM INF mgradm/cmd/cmd.go:67 > Executing command: config
9:01AM DBG shared/utils/exec.go:41 > Running: systemctl list-unit-files uyuni-server.service
⠋ podman inspect uyuni-server --format {{.Name}}
9:01AM DBG shared/utils/exec.go:67 > Running: podman ps -q -f name=uyuni-server
9:01AM TRC shared/connection.go:193 > Found container ID '369eefc56021'
9:01AM INF shared/connection.go:490 > Running supportconfig in  uyuni-server
⠋ podman exec uyuni-server supportconfig
>9:03AM DBG shared/utils/exec.go:50 > Running: podman cp uyuni-server:/var/log/scc_suse_yymmdd_hhmm.txz /tmp/mgradm-1390345991/uyuni-server-supportconfig.txz
⠋ podman exec uyuni-server rm /var/log/scc_suse_yymmdd_hhmm.txz
9:03AM DBG shared/utils/exec.go:50 > Running: podman cp uyuni-server:/var/log/scc_suse_250620_0901.txz.md5 /tmp/mgradm-1390345991/uyuni-server-supportconfig.txz.md5
9:03AM DBG shared/utils/exec.go:67 > Running: podman exec uyuni-server rm /var/log/scc_suse_yymmdd_hhmm.txz
9:03AM DBG shared/utils/exec.go:41 > Running: systemctl list-unit-files uyuni-server.service
⠋ supportconfig 
9:05AM DBG shared/utils/exec.go:67 > Running: systemctl cat uyuni-*
9:05AM DBG shared/utils/exec.go:67 > Running: find /etc/systemd/system -maxdepth 1 -name uyuni-*service
⠋ systemctl is-enabled uyuni-hub-xmlrpc@.service
9:05AM DBG shared/utils/exec.go:41 > Running: systemctl is-enabled uyuni-server.service
9:05AM DBG shared/utils/exec.go:67 > Running: podman inspect uyuni-hub-xmlrpc
9:05AM WRN shared/podman/support.go:40 > failed to run podman inspect uyuni-hub-xmlrpc error="failed to run podman inspect uyuni-hub-xmlrpc: exit status 125"
9:05AM DBG shared/utils/exec.go:67 > Running: podman inspect uyuni-hub-xmlrpc --format {{range .Mounts}}{{if eq .Type "bind"}} {{.Source}}{{end}}{{end}}
9:05AM WRN shared/podman/support.go:46 > failed to fetch the config files bound to container uyuni-hub-xmlrpc error="failed to run podman inspect uyuni-hub-xmlrpc: exit status 125"
9:05AM DBG shared/utils/exec.go:67 > Running: journalctl -u uyuni-hub-xmlrpc
9:05AM DBG shared/utils/exec.go:67 > Running: podman inspect uyuni-server
⠋ podman inspect uyuni-server --format {{range .Mounts}}{{if eq .Type "bind"}} {{.Source}}{{end}}{{end}}
9:05AM DBG shared/utils/exec.go:67 > Running: journalctl -u uyuni-server
9:05AM INF shared/utils/support.go:46 > Preparing the tarball
9:05AM DBG shared/utils/exec.go:67 > Running: hostname 
Error: failed to add . to tarball: open : no such file or directory