raihanjp commented on issue #8351: URL: https://github.com/apache/cloudstack/issues/8351#issuecomment-1853644096
the resolv.conf only have this and nslookup can't ping google.com ~~ nameserver 8.8.8.8 ~~ i added ~~ nameserver 192.168.10.1 ~~ finally the VR can ping and nslookup google.com, but the VR itself is not pingable and it can't ping it's own ip address. and the kubernetes still can't pull the image, i've tried with other image and it still has the same error. (s-1-vm = system VM & r-11-VM = VR) Does this ip route on the system vm and the VR matter? the VR name changed from the last image i post after i reboot the VR   -- 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]
