weizhouapache commented on issue #7653: URL: https://github.com/apache/cloudstack/issues/7653#issuecomment-1599228401
> > > @weizhouapache and @DaanHoogland Thank you, the logs are not really confirming anything for me. However, I made a video of me showing you the error to replicate it while grabbing a copy of what the log outputs. In this case, it fails to write new and recently created VMs entries to `/etc/hosts/` when terminating the VM, it seems to update perfectly fine and remove the entry. But for some reason, it's specifically failing to write an entry for new and other existing VMs that have been recently created. > > > You can view the video and get the log files here: https://privnote.com/UPggnDRK#Ycx61RQ0p PS This link will self-destruct within 50 mins > > > > > > @whitetiger264 just want to confirm > > > > * which cloudstack version do you use ? > > * was the cloudstack created from the correct template ? > > * how many guest IP ranges in the shared network ? > > * are the IPs in cloudstack VR correct ? (share "ip a" if possible) > > > > I noticed some errors like `Command 'dhcp_release $(ip route get xxx ' returned non-zero exit status 1` which I never saw before > > 1. I use version 4.18 but as mentioned I saw or noticed this with previous versions such as 4.17 > 2. I am not sure I understand this question, I created CloudStack from this source http://download.cloudstack.org/centos/$releasever/4.18/ and I used the correct System templated for 4.18 too by following the official upgrade documentation. > 3. I have one Guest Network called `public network` and in this network, I have: > > * 2 x /29 public ranges > * 3 x /28 public ranges > So 5 different ranges in total. Of which I currently have 18 VMs utilising from these ranges, fully publicly accessible. I also noticed now that my VirtualRouter also gets its Guest public IP from one of these ranges. > > 4. I believe so, though not 100% sure, I am new to Cloudstack and I followed documentation when I did the installation. I ssh into my VR now and ran `ip a` as requested: > > ``` > root@r-128-VM:~# ip a > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 > link/ether 1e:00:e9:00:00:4c brd ff:ff:ff:ff:ff:ff > altname enp0s3 > altname ens3 > inet 197.189.xxx.xxx/29 brd 197.189.xxx.xxx scope global eth0 > valid_lft forever preferred_lft forever > inet 129.232.xxx.xxx/28 brd 129.232.xxx.xxx scope global eth0 > valid_lft forever preferred_lft forever > inet 41.72.xxx.xxx/28 brd 41.72.xxx.xxx scope global eth0 > valid_lft forever preferred_lft forever > 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 > link/ether 0e:00:a9:fe:7e:67 brd ff:ff:ff:ff:ff:ff > altname enp0s4 > altname ens4 > inet 169.254.126.103/16 brd 169.254.255.255 scope global eth1 > valid_lft forever preferred_lft forever > root@r-128-VM:~# > ``` @whitetiger264 I would suggest you to create a shared network for each IP range. it will make configuration more simple. back to your issue, eth0 has only 3 public IPs attached. maybe there is no VMs on the other 2 IP ranges. can you please double-check ? -- 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]
