RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1451097 - First galera cluster bootstrap may fail if cluster has no data
Summary: First galera cluster bootstrap may fail if cluster has no data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Damien Ciabrini
QA Contact: Asaf Hirshberg
URL:
Whiteboard:
Depends On:
Blocks: 1451414
TreeView+ depends on / blocked
 
Reported: 2017-05-15 19:07 UTC by Damien Ciabrini
Modified: 2017-08-01 15:00 UTC (History)
12 users (show)

Fixed In Version: resource-agents-3.9.5-99.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1451414 (view as bug list)
Environment:
Last Closed: 2017-08-01 15:00:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
commit a09b17f79ef3dcde8843ee25bb52b506b6948e8e for downstream (5.23 KB, patch)
2017-05-16 12:56 UTC, Damien Ciabrini 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Github ClusterLabs resource-agents pull 939 0 None None None 2017-05-15 19:07:36 UTC
Red Hat Product Errata RHBA-2017:1844 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2017-08-01 17:49:20 UTC

Description Damien Ciabrini 2017-05-15 19:07:37 UTC 
Description of problem:
The resource agent selects the first node to go into Master state
based on the biggest commit version found on each node. If case no
data were written yet into the galera cluster, the current node is
selected as a "fallback" node to bootstrap the cluster.

The way the "fallback" node is selected is wrong because every node
takes a different decision, and this can yield to several nodes 
bootstrapping their own cluster instead of all nodes forming
a single cluster. 

Version-Release number of selected component (if applicable):
resource-agents-3.9.5-82.el7_3.10.x86_64

How reproducible:
Non-deterministic

Steps to Reproduce:
1. Deploy an HA overcloud with composable HA, galera resource on 3 dedicated nodes 

Actual results:
Sometimes more than one node can be selected as the bootstrap node, causing
the deploy to fail

Expected results:
A single node should be elected as bootstrap

Additional info:
Comment 2 Raoul Scarazzini 2017-05-16 08:14:49 UTC 
Here [1] the sosreports of two different deploys failed the same way.

[1] http://file.rdu.redhat.com/~rscarazz/BZ1451097/
Comment 4 Damien Ciabrini 2017-05-16 12:56:07 UTC 
Created attachment 1279321 [details]
commit a09b17f79ef3dcde8843ee25bb52b506b6948e8e for downstream
Comment 5 Damien Ciabrini 2017-05-16 12:57:34 UTC 
One need to apply in sequence the following commits from upstream:

a09b17f79ef3dcde8843ee25bb52b506b6948e8e (downstream version attached)
1fe6d7e9aca159a04e984d693dfcc47580bf5def
0265bcebb24427f5c76cfaa58c281c3aaead7d52
Comment 6 Oyvind Albrigtsen 2017-05-16 13:28:47 UTC 
Build with patches from comment #5.
Comment 8 Damien Ciabrini 2017-05-16 13:55:11 UTC 
Instruction for testing:

1. create a 3-node pacemaker cluster

  pcs cluster setup --name foo centos1 centos2 centos3 --force
  pcs cluster start --all

2. on all nodes, start from a clean mysql database in /var/lib/mysql

  rm -rf /var/lib/mysql
  mkdir /var/lib/mysql
  chown mysql. /var/lib/mysql
  restorecon /var/lib/mysql

3. create a galera resource, don't start it yet

  pcs resource create galera galera enable_creation=true wsrep_cluster_address='gcomm://centos1,centos2,centos3' meta master-max=3 --master --disable

4. monitor the cluster after the resource is enabled

  crm_mon -RrA
  pcs resource enable galera

The last-commit attribute from all nodes will be set to -1 because no WSREP commit has been integrated yet.

With the fix, on such start condition, the 3 nodes will always chose centos3 as a bootstrap node, as expected.
Comment 10 Damien Ciabrini 2017-05-17 14:59:33 UTC 
Additional comment, if the test is being run on a OpenStack HA overcloud, one should run the additional step on all nodes:

2b. let the resource agent use the default user for polling state 

  rm /etc/sysconfig/clustercheck
Comment 11 Udi Shkalim 2017-06-07 14:52:09 UTC 
Verified on resource-agents-3.9.5-99.el7.x86_64 with steps from comment #8
Comment 12 errata-xmlrpc 2017-08-01 15:00:11 UTC 
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://access.redhat.com/errata/RHBA-2017:1844
Note You need to log in before you can comment on or make changes to this bug.