So, it appears that this isn't really a bug but a case of needing to reconfigure the networking a bit after deployment as the AOI deployment is intended for test use rather than as a way of deploying an environment.
Anyway, the way to get around the problem was to move the external IP for my host, 192.168.1.8, to the br-vlan interface and then to add my external interface, ens3 to the br-vlan bridge configuration:
ip a d 192.168.1.8/24 dev ens3; ip a a 192.168.1.8/24 dev br-vlan; brctl addif br-vlan ens3
So, it appears that this isn't really a bug but a case of needing to reconfigure the networking a bit after deployment as the AOI deployment is intended for test use rather than as a way of deploying an environment.
Anyway, the way to get around the problem was to move the external IP for my host, 192.168.1.8, to the br-vlan interface and then to add my external interface, ens3 to the br-vlan bridge configuration:
ip a d 192.168.1.8/24 dev ens3; ip a a 192.168.1.8/24 dev br-vlan; brctl addif br-vlan ens3