Hi Nick, Have you started by building an "All-In-One" which should give you a completely functional test environment inside a single VM or bare metal machine? See https://docs.openstack.org/openstack-ansible/victoria/user/aio/quickstart.ht... The AIO will auto-configure everything for you which is then a good starting point for comparing with your real bare metal deployment. If you join the IRC channel #openstack-ansible we can try to help out. See https://docs.openstack.org/contributors/common/irc.html I don't see your config file attached here? Regards, Jonathan. On 16/07/2021 09:42, Nicola Ferrari (#554252) wrote:

Dears,

I'm new to the list. We're just trying to introduce a demo install of openstack in our network.

Our intention was to use 5 machine, already installed with ubuntu-mini 20.04.

ostack1 as control node ostack2 -| ostack3 -| AS COMPUTE NODE ostack4 -| ostack5 -|

ostack4 - ostack5 also as block storage node, they are connected on a direct storage (sas) where we deployed lvm with a vg named "cinder_volumes".

All nodes both are on a /24 network (192.168.32.0/24) behind a router (32.254) and also on a "private" network (10.255.255.0/24) which just interconnect nodes themselves.

We inteded to deploy openstack using openstack-ansible, available on github, last stable release. You can see our user_config as attachment.

setup-hosts playbook runs with no errors. setup-infrastructure playbook hangs on

RUNNING HANDLER [repo_server : reload nginx] **************************************************************************************** FAILED - RETRYING: reload nginx (1 retries left). fatal: [ostack1_repo_container-aabb6a12]: FAILED! => {"attempts": 5, "changed": false, "msg": "Unable to start service nginx: Job for nginx.service failed because the control process exited with error code.\nSee \"systemctl status nginx.service\" and \"journalctl -xe\" for details.\n"}

Looking at log I can see that nginx coudn't start due to "Cannot assign requested address: 99" error.

I suppose that must be a mistake in the deploy file?

Many thanks for your suggestion, and pls, be sorry for my poor english :)

Nick