The behaviour of creating the FIP in a snat namespace is expected. What is not expected is that the FIP is not migrated to the corresponding compute when the port is associated with a VM. There is a previously filed bug that describes the same situation as yours (without the heat templates): https://bugs.launchpad.net/neutron/+bug/1718788. It was fixed with this patch https://review.openstack.org/#/q/I6b1f3ffc3c3336035632f6a82d3a87b3be57b403 during the Queens cycle. As you can see, it was backported to Pike. Do you have this fix?
Marking incomplete until we hear back from submitter
Hi Piotrrr,
The behaviour of creating the FIP in a snat namespace is expected. What is not expected is that the FIP is not migrated to the corresponding compute when the port is associated with a VM. There is a previously filed bug that describes the same situation as yours (without the heat templates): https:/ /bugs.launchpad .net/neutron/ +bug/1718788. It was fixed with this patch https:/ /review. openstack. org/#/q/ I6b1f3ffc3c3336 035632f6a82d3a8 7b3be57b403 during the Queens cycle. As you can see, it was backported to Pike. Do you have this fix?
Marking incomplete until we hear back from submitter