KobesM commented on issue #10163: URL: https://github.com/apache/cloudstack/issues/10163#issuecomment-2583829529
A small update from my side... I verified if manually adding the route to the nfs server would work: After logging into the SSVM the `/var/log/cloud.log` has the following warning logged as stated earlier: ``` 2025-01-08T21:53:23,824 WARN [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-2:[]) Execution of process [3611] for command [/bin/bash -c ip route add 192.168.1.21 via null ] failed. ``` At this point there is no route to 192.168.1.21: ``` root@s-2-VM:~# ip route default via 10.143.71.1 dev eth2 10.143.51.0/24 dev eth1 proto kernel scope link src 10.143.51.111 10.143.71.0/24 dev eth2 proto kernel scope link src 10.143.71.102 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.17.84 192.168.1.22 via 10.143.51.1 dev eth1 ``` So I manually added the route: ``` root@s-2-VM:~# ip route add 192.168.1.21 via 10.143.51.1 ``` The route to 192.168.1.21 now does exist: ``` root@s-2-VM:~# ip route default via 10.143.71.1 dev eth2 10.143.51.0/24 dev eth1 proto kernel scope link src 10.143.51.111 10.143.71.0/24 dev eth2 proto kernel scope link src 10.143.71.102 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.17.84 192.168.1.21 via 10.143.51.1 dev eth1 192.168.1.22 via 10.143.51.1 dev eth1 ``` Also the `/var/log/cloud.log` reports it found the nfs server and created the required folders: ``` 2025-01-10T19:34:57,532 INFO [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-5:[]) Determined host nfs01.local.ironhive.nl corresponds to IP 192.168.1.21 2025-01-10T19:34:57,927 INFO [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-5:[]) snapshots directory created/exists on Secondary Storage. 2025-01-10T19:34:57,939 INFO [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-5:[]) volumes directory created/exists on Secondary Storage. ``` At this point I was also able to upload an image from the UI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
