Symptoms
If new VM is created without public IP, its bridged interface is disconnected from VM. It can be seen by (-) sign in the following command's output:
# pctl list 1.testwin --info | grep net
Boot order: hdd0 cdrom0 fdd0 net0 net1
net0 (+) dev='vme661b3e25.0' ifname='eth0' type=routed mac=123C42D5C0E3 card=e1000 ips='172.28.1.161/255.255.0.0 '
net1 (-) dev='vme661b3e25.1' ifname='eth1' network='Bridged' mac=123C422329FB card=e1000
As result when customer adds new public IP, it is getting added to net1, but not seen inside VM because net1 is disabled:
# pctl list 1.testwin --info | grep net
Boot order: hdd0 cdrom0 fdd0 net0 net1
net0 (+) dev='vme661b3e25.0' ifname='eth0' type=routed mac=123C42D5C0E3 card=e1000 ips='172.28.1.161/255.255.0.0 '
net1 (+) dev='vme661b3e25.1' ifname='eth1' network='Bridged' mac=123C422329FB card=e1000 ips='46.226.92.10/255.255.255.0 ' gw='46.226.92.1'
After restarting the VM, new IP can be seen inside it.
Cause
Bug CCU-8206
Resolution
The issue has been reported to the development team as a bug CCU-8206. It will be fixed in future versions of POA. Please contact your Account Manager to trace the status of the issue.
To workaround the issue, it is necessary to restart the affected VM.