Containerized galera fail to deploy if stack name use capital letters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Damien Ciabrini |
Bug Description
When deploying a containerized Pike stack or upgrading from Ocata to containerized Pike, the galera resource starts to FQDN to identify nodes and a new configuration that maps pacemaker node name to galera FQDN.
Currently the mapping logics in puppet-tripleo is broken if the stack name uses capital letters. Consequently, the stack creation/update will fail at step 2 when the galera resource agent refuses to start galera. The following error is reported by pcs status:
Failed Actions:
* galera_start_0 on galera-bundle-1 'not configured' (6): call=13, status=complete, exitreason='Could not determine galera name from pacemaker node <foobar-
last-
* galera_start_0 on galera-bundle-2 'not configured' (6): call=13, status=complete, exitreason='Could not determine galera name from pacemaker node <foobar-
last-
* galera_start_0 on galera-bundle-0 'not configured' (6): call=13, status=complete, exitreason='Could not determine galera name from pacemaker node <foobar-
last-
Changed in tripleo: | |
importance: | Undecided → High |
Fix proposed to branch: master /review. openstack. org/544384
Review: https:/