Hi,
I am just evaluating Proxmox, and have come across a strange issue.
I have made a template Ubuntu 18.04 server (with netplan by default - setup with DHCP during install, disabled ipv6 after install), and cloned it a few times.
Whenever I clone it, it gets a new mac - good, but it gets the same ip address assigned via dhcp - bad.
I have access to a Xen box, so tried the same thing (fresh install, followed same steps - it is on a different subnet, so that is different, but uses the same DHCP server)... it works. All new vms get a new mac address AND a new ip address - all good.
Went back to the Proxmox VMs, and removed netplan, and everything worked - new clones get new mac addresses and ip addresses, so at least something works.
Cloned some of the original VMs again, and still get new mac addresses but same ip address assigned.
I am not too familiar with netplan or Proxmox, but something strange is happening and I am not sure how to debug it. As mentioned, it does not seem to replicate behaviour on a Xen box.
Any pointers on debugging would be appreciated.
Regards
Colin
I am just evaluating Proxmox, and have come across a strange issue.
I have made a template Ubuntu 18.04 server (with netplan by default - setup with DHCP during install, disabled ipv6 after install), and cloned it a few times.
Whenever I clone it, it gets a new mac - good, but it gets the same ip address assigned via dhcp - bad.
I have access to a Xen box, so tried the same thing (fresh install, followed same steps - it is on a different subnet, so that is different, but uses the same DHCP server)... it works. All new vms get a new mac address AND a new ip address - all good.
Went back to the Proxmox VMs, and removed netplan, and everything worked - new clones get new mac addresses and ip addresses, so at least something works.
Cloned some of the original VMs again, and still get new mac addresses but same ip address assigned.
I am not too familiar with netplan or Proxmox, but something strange is happening and I am not sure how to debug it. As mentioned, it does not seem to replicate behaviour on a Xen box.
Any pointers on debugging would be appreciated.
Regards
Colin