OK, got it. I'm reconfiguring the network, hopefully better luck next time!

Thanks all!

On Mon, Mar 17, 2025 at 6:13 PM Jonathan Rosser <jonathan.rosser@rd.bbc.co.uk> wrote:

On 17/03/2025 17:42, Kerem Celiker wrote:
> Hey Sarah,
>
> Your containers are using the same IP range as your physical network
> (both are on 10.0.1.x) and thats causing chaos :( when you try to
> connect to a container (like your repo server), the network gets
> confused and HAProxy throws a 503 Service Unavailable error..
>
> Basically the IPs are clashing, and traffic is getting tangled up.
>
> just leave your physical network alone and just shift your containers
> to a different IP range like 192.168.0.x - this way everyone stays in
> their own lane and the conflicts disappear and you re good to go.
>
For openstack-ansible the default behaviour is to use addresses from the
openstack management network for both the physical hosts and the LXC
containers, as described though all our documentation.

It is possible to use seperate network ranges for the physical hosts,
but this requires special configuration to work correctly as described
here
https://docs.openstack.org/openstack-ansible/latest/reference/inventory/configure-inventory.html#having-ssh-network-different-from-openstack-management-network

Regards,
Jonathan.



--
[s]