Comment 2 for bug 1578106

Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote : Re: 9.0 mitaka mos is failed to deploy with nodes in error state

It looks like deployment failed because fuel can't install mysql and rabbitmq clusters in HA mode, we can see many puppet errors in logs, like:

 (/Stage[main]/Cluster::Mysql/Exec[wait-initial-sync]) Failed to call refresh: mysql -uclustercheck -pd83wmbYJXsbpeo9ZCJz3sJI9 -Nbe "show status like 'wsrep_local_state_comment'" | grep -q -e Synced && sleep 10 returned 1 instead of one of [0]

 Could not prefetch mysql_user provider 'mysql': Execution of '/usr/bin/mysql --defaults-extra-file=/root/.my.cnf -NBe SELECT CONCAT(User, '@',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)

(/Stage[main]/Rabbitmq::Install::Rabbitmqadmin/Staging::File[rabbitmqadmin]/Exec[/var/lib/rabbitmq/rabbitmqadmin]/returns) change from notrun to 0 failed: curl -k --noproxy localhost --retry 30 --retry-delay 6 -f -L -o /var/lib/rabbitmq/rabbitmqadmin http://nova:kOVE8QMA6taaje1mZZjHCbZe@localhost:15672/cli/rabbitmqadmin returned 7 instead of one of [0]

It is blocker for QA team because many test configurations which we use to run Tempest tests failed with this error.
Priority changed to Critical because deployment of the environment failed and we don't have a workaround yet.