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.
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 https://github.com/uyuni-project/uyuni/issues/9023 but this did not resolve it for me.
(I've manually changes the fqdn for privacy, but the two match)
Uyuni host vm (Leap micro 5.5)
In container, via "mgrctl term"
DNS lookup is resolved correctly inside and outside of the container
"mgradm upgrade podman" also fails with the same error.
Please advise. Thanks.
Steps to reproduce
As above
Uyuni version
Uyuni proxy version (if used)
No response
Useful logs
No response
Additional information
No response