rubygem-staypuft: [nonHA] Puppet error: Stage[main]/Quickstack::Pacemaker::Galera/Exec[galera-online]/returns change from notrun to 0 failed: /usr/bin/clustercheck >/dev/null returned 1 instead of one of [0] - the deployment gets paused with error. Environment: openstack-foreman-installer-3.0.3-1.el7ost.noarch ruby193-rubygem-staypuft-0.5.1-1.el7ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch rhel-osp-installer-client-0.5.1-1.el7ost.noarch openstack-puppet-modules-2014.2.6-1.el7ost.noarch rhel-osp-installer-0.5.1-1.el7ost.noarch Steps to reproduce: 1. Install rhel-osp-installer. 2. Create/run a deployment with a single controller + 1 compute. Result: The deployment gets paused with error. Analyzing the reports I see this puppet error: Stage[main]/Quickstack::Pacemaker::Galera/Exec[galera-online]/returns change from notrun to 0 failed: /usr/bin/clustercheck >/dev/null returned 1 instead of one of [0] - the deployment gets paused with error. Expected result: This puppet error shouldn't occur.
Created attachment 964361 [details] /var/log/messages file from the controller
selinux is preventing pacemaker from starting galera. E.g., starting the pacemaker galera resource agent looked good at first: Master/Slave Set: galera-master [galera] Slaves: [ pcmk-maca25400702877 ] but it never got promoted to Master. After setting selinux to permissive, pacemaker was able to start galera. The root cause looks like (from /var/log/audit/audit.log): type=AVC msg=audit(1417646108.342:337): avc: denied { read } for pid=18968 comm="mysqld_safe" name="cores" dev="dm-0" ino=51125914 scontext=system_u:sys m_r:mysqld_safe_t:s0 tcontext=system_u:object_r:cluster_var_lib_t:s0 tclass=dir
Created attachment 964366 [details] contains: audit.log mariadb.log messages pacemaker.log audit.log includes the mysql-related AVC. Other pertinent log files included.
type=AVC msg=audit(1417638763.636:183): avc: denied { read } for pid=19681 comm="mysqld_safe" name="cores" dev="dm-0" ino=51125914 scontext=system_u:system_r:mysqld_safe_t:s0 tcontext=system_u:object_r:cluster_var_lib_t:s0 tclass=dir $ setsebool daemons_enable_cluster_mode 1 Will review with Lon and Miroslav.
Yes, we have $ setsebool daemons_enable_cluster_mode 1 for these cases.
Verified: Environment: rhel-osp-installer-client-0.5.1-1.el7ost.noarch openstack-puppet-modules-2014.2.6-1.el7ost.noarch openstack-foreman-installer-3.0.5-1.el7ost.noarch rhel-osp-installer-0.5.1-1.el7ost.noarch ruby193-rubygem-staypuft-0.5.3-1.el7ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch The reported issue doesn't re-produce.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0156.html