Open
Description
ISSUE TYPE
- Bug Report
COMPONENT NAME
secondarystoragevm
CLOUDSTACK VERSION
4.20.0.0
CONFIGURATION
Advanced Networking
Single Zone
physical network
- Management gw 10.143.51.1, mask 255.255.255.0, vlan://untagged, start 10.143.51.151, end 10.143.51.200
- Public gw 10.143.51.1, mask 255.255.255.0, vlan://51, start 10.143.51.101, end 10.143.51.150
OS / ENVIRONMENT
Almalinux 9.5 Manager and KVM hosts
SUMMARY
I just deployed Apache Cloudstack 4.20 as a fresh install but can't upload images to the secondairy storage. When uploading the image using the UI I receive the following error "Failed to upload Template - Error: Network Error".
STEPS TO REPRODUCE
When logging into the secondarystoragevm (ssh from KVM host) i found the following errors in the /var/log/cloud.log:
2025-01-05T20:45:36,290 WARN [cloud.agent.Agent] (agentRequest-Handler-3:[]) Caught: com.cloud.utils.exception.CloudRuntimeException: Failed to get root directory from secondary storage URL [nfs://<nfs path>], using NFS version [null], due to [Unable to mount /192.168.1.21:<nfs path> at /mnt/SecStorage/d096bb1f-552a-3424-ab65-63c694685108 due to mount.nfs: No route to host].
and
2025-01-05T20:19:35,110 WARN [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-2:[]) Execution of process [3587] for command [/bin/bash -c ip route add 192.168.1.21 via null ] failed.
Requesting the route table there is no route to 192.168.1.21 (nfs server):
# ip route
default via 10.143.51.1 dev eth2
10.143.51.0/24 dev eth1 proto kernel scope link src 10.143.51.196
10.143.51.0/24 dev eth2 proto kernel scope link src 10.143.51.101
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.46.109
192.168.1.22 via 10.143.51.1 dev eth1
EXPECTED RESULTS
System VM would add a route to the NFS server.
ACTUAL RESULTS
It seams to me for some reason the system VM is not able to add the correct route to the NFS server, which in this case is a Synology NAS. The log states it wants to add a static route using the device "null"? I found the consoleproxy vm does not have this issue and adds the static route to 192.168.1.21 without issues (Synology NAS also acts as the internal DNS server).
Metadata
Metadata
Assignees
Type
Projects
Status
ready for Review