Removing default mysql accounts fails during step1 when using pacemaker HA
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
We have remove_
However, this fails during step1 of the deployment because the galera ocf resource is not defined in pacemaker until step2, so there is no database running during step1.
Interestingly, this does not fail the puppet run during step1, which is why our ovb HA jobs are not failing. You just end up with this error message in the puppet logs:
Oct 13 09:04:42 overcloud-
:Base::
Firewall:
Warning: Scope(Haproxy:
prefetch mysql_user provider 'mysql': Execution of '/usr/bin/mysql -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/lib/mysql
/mysql.sock' (2 \"No such file or directory\
local MySQL server through socket '/var/lib/
Oct 13 09:04:42 overcloud-
-puppet/
tack/puppet-
Oct 13 09:04:42 overcloud-
You can see the error above, but puppet still returned 2.
This can't be quite misleading to people trying to debug failed deployments as they may go chasing the cause of this error, not realizing that a puppet return code of 2 actually means "success". In reality, they may have a later failure that is the real cause of their problem.
We should fix our manifests so that we do not attempt to access the database during step1 of pacemaker deployments.
For reference, the above log comes from this job:
http://
Changed in tripleo: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Emilien Macchi (emilienm) |
milestone: | none → ocata-1 |
Does this affect Newton?