iishitahere commented on issue #10163: URL: https://github.com/apache/cloudstack/issues/10163#issuecomment-2581889072
> > Hi @DaanHoogland , I have reviewed the issue and my approach to address it. The problem seems to be that the system VM is unable to add the correct route to the NFS server, as indicated by the error logs showing the use of null in the route table, which leads to the "No route to host" error. > > My approach to solve this issue would involve the following steps: > > Investigate Route Table Configuration: I'll start by reviewing the route table configuration on the system VM and identifying why the static route to the NFS server is not being added correctly. It seems that the null value is being passed where an actual device or gateway should be specified. > > Verify Network Interfaces and Gateway Configuration: I will check the network interfaces on the secondary storage VM and confirm that the correct gateway is set, ensuring it is able to route traffic to the 192.168.1.21 NFS server. > > Check NFS Mount Configuration: I'll verify the NFS configuration and ensure that the system VM has proper access permissions and that the NFS server is reachable from the secondary storage VM. > > Manually Add Route (Testing): I’ll test adding the static route manually using the ip route add command to see if it resolves the issue and confirm that the system VM can reach the NFS server. > > Implement Solution in Code: Once I have identified the root cause, I will make any necessary changes to the code to ensure the system VM correctly adds the route to the NFS server. This may involve updating the networking or route handling logic within CloudStack. > > I will proceed with debugging the issue and keep you updated on my progress. Let me know if there are any additional details that could assist in troubleshooting. > > Best Regards, Ishita Jaiswal > > @iishitahere in my opinion, the root cause is obvious and the fix seems simple you can create a PR if you have the fix > > by the way, do you have an environment to verify the fix ? Yes, I do have the environment to verify the fix. I’m currently working on the PR and will update you once it's ready. I will submit by day after tomorrow for sure! -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
