openstack
/
tripleo-heat-templates
Code Issues Proposed changes

Use --force when creating pacemaker resources 

pcs-0.10.14-6 introduced enforce validation at resources creation time.
Unfortunately this doesn't work in our use case as puppet runs on the
host but the necessary binaries are installed inside the containers.

Let's try using --force to workaround.

Closes-Bug: #1997939

Change-Id: Id7616ebceb820d9799661c0fbc5f3f234f421ea3
This commit is contained in:
Luca Miccini 2022-11-28 19:38:15 +01:00
parent 676a60a507
commit 59300dfb30
3 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
deployment/database/mysql-pacemaker-puppet.yaml
View File

@ -182,6 +182,9 @@ outputs:
tripleo::profile::pacemaker::database::mysql_bundle::sst_method: {get_param: MysqlGaleraSSTMethod}
tripleo::profile::pacemaker::database::mysql_bundle::mariabackup_user: {get_param: MysqlMariabackupUser}
tripleo::profile::pacemaker::database::mysql_bundle::mariabackup_password: {get_param: MysqlMariabackupPassword}
# starting from pcs-0.10.14-6 enforces validations but this doesn't work when running
# outside the respective containers. we need to use --force to overcome this.
tripleo::profile::pacemaker::database::mysql_bundle::force_ocf: true
# BEGIN DOCKER SETTINGS #
puppet_config:
config_volume: mysql

3
deployment/database/redis-pacemaker-puppet.yaml
View File

@ -150,6 +150,9 @@ outputs:
expression: concat($.data.rightSplit(separator => ":", maxSplits => 1)[0], ":pcmklatest")
tripleo::profile::pacemaker::database::redis_bundle::redis_docker_control_port: 3124
tripleo::profile::pacemaker::database::redis_bundle::container_backend: {get_param: ContainerCli}
# starting from pcs-0.10.14-6 enforces validations but this doesn't work when running
# outside the respective containers. we need to use --force to overcome this.
tripleo::profile::pacemaker::database::redis_bundle::force_ocf: true
tripleo::stunnel::manage_service: false
tripleo::stunnel::foreground: 'yes'
tripleo::profile::pacemaker::database::redis_bundle::tls_proxy_bind_ip:

3
deployment/rabbitmq/rabbitmq-messaging-rpc-pacemaker-puppet.yaml
View File

@ -150,6 +150,9 @@ outputs:
KOLLA_CONFIG_STRATEGY: COPY_ALWAYS
LANG: en_US.UTF-8
LC_ALL: en_US.UTF-8
# starting from pcs-0.10.14-6 enforces validations but this doesn't work when running
# outside the respective containers. we need to use --force to overcome this.
tripleo::profile::pacemaker::rabbitmq_bundle::force_ocf: true
service_config_settings: {get_attr: [RabbitmqBase, role_data, service_config_settings]}
# BEGIN DOCKER SETTINGS
puppet_config: