Please, could you check if it’s a name resolving issue with your update-vm?
If yes, is your update-vm is a fedora VM with systemd-resolved >= 249
?
If yes, then read #7429.
Please, could you check if it’s a name resolving issue with your update-vm?
If yes, is your update-vm is a fedora VM with systemd-resolved >= 249
?
If yes, then read #7429.