"mgr podman" commands fail with common error

[digdilem-work]

Problem description

I'm aware of several other issues raised reporting similar issues, but I've not found a resolution in those.

Server was migrated from RPM to Podman about 3 weeks ago. Most things are fine, but I'm concerned that this will prevent us upgrading to any future versions. We have a lot of changes invested since the upgrade, so starting the migration over is very much something we don't want to do.

During the upgrade I created a new vm, named it uyuni02 and as per the guide, turned off the original and then changed the ip and hostname of the new vm to that of the original. The clients are checking in, we've worked out scheduled events and things seem good, apart from this.

I have tried "mgradm uninstall --force" and "mgadm install podman" as advised in #9023 but this did not resolve it for me.

(I've manually changes the fqdn for privacy, but the two match)

ata-oxy-uyuni01:/home/simon # mgradm inspect
2:29PM INF Welcome to mgradm
2:29PM INF Executing command: inspect
2:29PM INF Computed image name is registry.opensuse.org/uyuni/server:latest
2:29PM INF Pull Policy is always. Presence of RPM image will be checked and if it's not present it will be pulled from registry
2:29PM INF Cannot find RPM image for registry.opensuse.org/uyuni/server:latest
2:29PM INF Running podman pull registry.opensuse.org/uyuni/server:latest
Trying to pull registry.opensuse.org/uyuni/server:latest...
Getting image source signatures
Copying blob 0a5f8240e04b skipped: already exists
Copying blob 4dcdc701cb4a skipped: already exists
Copying blob 3e004aa9a8af skipped: already exists
Copying config 1b794a1eb8 done   |
Writing manifest to image destination
1b794a1eb81cf14fe337f9bf243e0cd56f81c4af9bc3e1bb259396f702a6f49e
Error: inspect command failed: cannot inspect data: cannot read config: While parsing config: line `ata-oxy-uyuni01.company.com` doesn't match format

Uyuni host vm (Leap micro 5.5)

ata-oxy-uyuni01:/home/simon # hostname -f
ata-oxy-uyuni01.company.com

In container, via "mgrctl term"

uyuni-server:/ # hostname -f
uyuni-server.mgr.internal

DNS lookup is resolved correctly inside and outside of the container

uyuni-server:/ # nslookup ata-oxy-uyuni01.company.com
Server:         10.89.0.1
Address:        10.89.0.1#53

Name:   ata-oxy-uyuni01.company.com
Address: 172.30.101.199

"mgradm upgrade podman" also fails with the same error.

Please advise. Thanks.

Steps to reproduce

As above

Uyuni version

2024-08 Podman

Uyuni proxy version (if used)

No response

Useful logs

No response

Additional information

No response