Hi, I would enable Debug logging in the neutron.conf file for neutron_server server service, restart it and then look at the neutron server log stored in the kolla_logs docker volume. To read this log you can for example exec into neutron_server container and change to /var/log/kolla directory. BR, Piotr Misiak On Fri, 3 Nov 2023 at 18:07 Bursztynowski Dariusz < dariusz.bursztynowski@pw.edu.pl> wrote:
I've installed OpenStack (zed) on a Raspberry Pi cluster using kolla-ansible (version tagged for zed), and all containers are healthy except the neutron_server which is suspended in 'health: starting' state.
Network related part of OpenStack seems not to work (snippet form running init-runonce): Configuring neutron. HttpException: 503: Server Error for url: http://192.168.1.60:9696/v2.0/routers, No server is available to handle this request.: 503 Service Unavailable. However, at least some commands not related to networking seem to work as expected (e.g., I can create an image which is reported by openstack image list as 'active').
There are four Raspberry Pi 4B in the cluster (2 x 4GB RAM and 2 x 8GB RAM). They run Debian 11 (bullseaye). Kolla-ansible has been used for the installation strictly following the guidelines form https://docs.openstack.org/kolla-ansible/zed/user/quickstart.html.
Notably, I'm using a specific (weird?) configuration of networking on my Pis to mimic two network interfaces on each host as kolla-ansible expects. These are provided as interfaces of veth pairs (more details on that can be found in my report here: https://bugs.launchpad.net/neutron/+bug/2042598). Is it possible that this setup rises problems?
I've already contacted OpenStack folks and they see no evident symptoms of neutron bug, suggesting a problem with deployment. Reported a bug to kolla-ansible here: https://bugs.launchpad.net/kolla-ansible/+bug/2042372, but do not know how fas they react there.
I could try to install other versions but maybe there's a smarter ways to cope with the problem. Any suggestion will be welcome.