Open Stack

Hi Dmitriy,

Yes I just spotted that myself as well. Thanks

Regards,
Derek

> On 6 Sep 2022, at 14:41, Dmitriy Rabotyagov <noonedeadpunk at gmail.com> wrote:
> 
> Hi,
> 
> These 2 containers are the only ones that should have a storage
> network in them. So I would assume that failure to start containers is
> related to the storage net. Please, kindly check that br-stor is
> configured correctly on hosts and defined in openstack-user-config.yml
> 
> вт, 6 сент. 2022 г. в 13:25, Derek O keeffe <derekokeeffe85 at yahoo.ie>:
>> 
>> Hi,
>> 
>> I recently successfully installed OSA and I am now trying to install it again from scratch with all the configuration changes I needed in place.
>> 
>> Unfortunately this time around it is failing on setup_hosts.yml here:
>> 
>> TASK [lxc_container_create : Create container (dir)] ******************************************************************
>> ok: [infra1_memcached_container-b92f4db7 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_rabbit_mq_container-d286a482 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_utility_container-05f756fc -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_galera_container-5beef059 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_aodh_container-639f5ad8 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_neutron_server_container-f67e972d -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_horizon_container-dfeaa0dc -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_placement_container-350e4ede -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_heat_api_container-82cbd764 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_nova_api_container-b30c38d1 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_repo_container-f16e50a9 -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_ceilometer_central_container-910a888f -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_keystone_container-32dcd68b -> infra1(CONTROLLER_IP_ADDRESS)]
>> ok: [infra1_gnocchi_container-30ccb451 -> infra1(CONTROLLER_IP_ADDRESS)]
>> fatal: [infra1_cinder_api_container-840a18bb -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_cinder_api_container-840a18bb ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_cinder_api_container-840a18bb", "state": "stopped"}, "msg": "The container [ infra1_cinder_api_container-840a18bb ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1}
>> fatal: [infra1_glance_container-b50e16a6 -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_glance_container-b50e16a6 ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_glance_container-b50e16a6", "state": "stopped"}, "msg": "The container [ infra1_glance_container-b50e16a6 ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1}
>> 
>> I don't understand how 14 containers are fine (can be attached to and commands run through lxc-attach) and 2 containers are failing. I have a deploy host, controller and two computes all with a fresh install of Ubuntu 20.04. The bootstrap_ansible script ran fine on the deploy host and the setup_hosts playbook ran through fully as after the above it skipped cinder and glance containers every where else.  Can anybody please point me in the direction of getting more info or a possible cause. Thanks in advance.
>> 
>