Comment 12 for bug 2003925

2023-02-16 12:02:37 metadataserver.api_twisted: [info] Trying to create vmhost for deployment for node fptpn3 (chief-orca)
2023-02-16 12:02:40 metadataserver.api_twisted: [critical] Failed to process status message instantly.
        Traceback (most recent call last):
          <...twisted and orm...>
          File "/snap/maas/x1/lib/python3.10/site-packages/metadataserver/api_twisted.py", line 505, in _processMessage
            _create_vmhost_for_deployment(node)
          File "/snap/maas/x1/lib/python3.10/site-packages/metadataserver/api_twisted.py", line 265, in _create_vmhost_for_deployment
            discover_and_sync_vmhost(pod, node.owner)
          File "/snap/maas/x1/lib/python3.10/site-packages/maasserver/vmhost.py", line 88, in discover_and_sync_vmhost
            raise PodProblem(str(error)) from error
        maasserver.exceptions.PodProblem: Failed talking to pod: Pod 10: Failed to connect to the LXD REST API: HTTPSConnectionPool(host='172.16.1.4', port=8443): Max retries exceeded with url: /1.0?project=maas (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f52921f9db0>: Failed to establish a new connection: [Errno 113] No route to host'))

Meanwhile, `172.16.1.48` is reported in MAAS UI for `chief-orca`, while `172.16.1.4` was the machine's IP during commissioning.