Open Stack

Hey Derek,

Connection to MySQL by default happens from utility container. While
running utility-install.yml playbook, it should install mysqlclient as well
deploy my.cnf file to it.

You should check if this file has been created and if it contains valid
credentials for login.
If it's not you should try rerunning this specific playbook.
Also if it has failed during previous run, likely you also don't have
proper virtualenv, so you should consider adding `-e venv_rebuild=true` to
the playbook execution.

вт, 26 апр. 2022 г., 12:21 Derek O keeffe <derekokeeffe85 at yahoo.ie>:

> Hi all,
>
> We get the following error in the openstack.osa.db_setup : Create
> database for service task:
>
> failed: [infra1_keystone_container-e54c8ba5 ->
> infra1_utility_container-1a1eb7ce(xx.xx.xx.xxx)] (item={'name': 'keystone',
> 'users': [{'username': 'keystone', 'password': 'PASSWORD'}]}) =>
> {"ansible_loop_var": "item", "changed": false, "item": {"name": "keystone",
> "users": [{"password": "PASSWORD", "username": "keystone"}]}, "msg":
> "unable to connect to database, check login_user and login_password are
> correct or /root/.my.cnf has the credentials. Exception message: (2003,
> \"Can't connect to MySQL server on 'xx.xx.xx.xxx' ([Errno 111] Connection
> refused)\")"}
>
> Also, ansible galera_container -m shell -a "mysql -h localhost -e 'show
> status like \"%wsrep_cluster_%\";'" is different to the example output:
>
> infra1_galera_container-90dd1571 | CHANGED | rc=0 >>
> Variable_name Value
> wsrep_cluster_weight 1
> wsrep_cluster_capabilities
> wsrep_cluster_conf_id 1
> wsrep_cluster_size 1
> wsrep_cluster_state_uuid c06b8107-c53a-11ec-a54c-a20664362f6c
> wsrep_cluster_status Primary
>
> We checked our infra node and all the containers are present and mysql is
> installed on the infra1-galera-container and port 3306 is open.
>
> MariaDB [(none)]> show databases;
> +--------------------+
> | Database                    |
> +--------------------+
> | information_schema   |
> | mysql                          |
> | performance_schema |
> | sys                              |
> +--------------------+
> 4 rows in set (0.001 sec)
>
>
> We are not sure what is causing this and it could possibly be that we have
> forgotten/skipped/missed a configuration step but we have gone over the
> process multiple times and cannot see what we may have missed. The previous
> playbooks did have a lot of "skipped" results
>
> compute1                   : ok=120  changed=2    unreachable=0
> failed=0    skipped=31   rescued=0    ignored=0
> compute2                   : ok=120  changed=2    unreachable=0
> failed=0    skipped=31   rescued=0    ignored=0
> infra1                     : ok=156  changed=3    unreachable=0
> failed=0    skipped=31   rescued=0    ignored=0
> infra1_aodh_container-7c703324 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_ceilometer_central_container-7590db72 : ok=89   changed=36
>  unreachable=0    failed=0    skipped=5    rescued=0    ignored=0
> infra1_cinder_api_container-91806531 : ok=89   changed=36   unreachable=0
>   failed=0    skipped=5    rescued=0    ignored=0
> infra1_galera_container-90dd1571 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_glance_container-fff39ac4 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_gnocchi_container-ffd32a8b : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_heat_api_container-a4079838 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_horizon_container-9c041ec0 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_keystone_container-e54c8ba5 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_memcached_container-dc50bcd8 : ok=89   changed=36   unreachable=0
>   failed=0    skipped=5    rescued=0    ignored=0
> infra1_neutron_server_container-bfc4d0d2 : ok=92   changed=37
>  unreachable=0    failed=0    skipped=5    rescued=0    ignored=0
> infra1_nova_api_container-f231bb13 : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_placement_container-108d79df : ok=89   changed=36   unreachable=0
>   failed=0    skipped=5    rescued=0    ignored=0
> infra1_rabbit_mq_container-50ca98ed : ok=89   changed=36   unreachable=0
>   failed=0    skipped=5    rescued=0    ignored=0
> infra1_repo_container-ccade01d : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> infra1_utility_container-1a1eb7ce : ok=89   changed=36   unreachable=0
> failed=0    skipped=5    rescued=0    ignored=0
> localhost                  : ok=19   changed=0    unreachable=0
> failed=0    skipped=14   rescued=0    ignored=0
>
>
> compute1                   : ok=0    changed=0    unreachable=0
> failed=0    skipped=10   rescued=0    ignored=0
> compute2                   : ok=0    changed=0    unreachable=0
> failed=0    skipped=10   rescued=0    ignored=0
> infra1                     : ok=38   changed=0    unreachable=0
> failed=0    skipped=35   rescued=0    ignored=0
> infra1_galera_container-90dd1571 : ok=69   changed=3    unreachable=0
> failed=0    skipped=12   rescued=0    ignored=0
> infra1_memcached_container-dc50bcd8 : ok=16   changed=0    unreachable=0
>   failed=0    skipped=4    rescued=0    ignored=0
> infra1_rabbit_mq_container-50ca98ed : ok=69   changed=33   unreachable=0
>   failed=0    skipped=14   rescued=0    ignored=0
> infra1_utility_container-1a1eb7ce : ok=40   changed=18   unreachable=0
> failed=0    skipped=11   rescued=0    ignored=0
>
>
> A lot were around Galera tasks but we are not sure if they were skipped
> intentionally as the playbooks ran to completion.
> Any help or troubleshooting steps would be appreciated. Thanks in advance.
>
>
> Regards,
> Derek
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220426/d2076b25/attachment.htm>