corosync runtime totem.token for pacemaker cluster is 1650ms on RHOSP16

Solution Verified - Updated -

Issue

After deployment, corosync runtime totem.token for pacemaker cluster is 1650ms on RHOSP16:

# corosync-cmapctl |grep totem.token
runtime.config.totem.token (u32) = 1650      <--------------------------
runtime.config.totem.token_retransmit (u32) = 392
runtime.config.totem.token_retransmits_before_loss_const (u32) = 4
runtime.config.totem.token_warning (u32) = 75

It is expected to be 10000ms as defined in ansible playbook:

# grep corosync_token_timeout /var/lib/mistral/config-download-latest/* -R
/var/lib/mistral/config-download-latest/Controller/config_settings.yaml:corosync_token_timeout: 10000
/var/lib/mistral/config-download-latest/group_vars/Controller:  corosync_token_timeout: 10000

There is also a commit in previous version to specify totem.token value as 10000ms when setting up pacemaker cluster during deployment.

Environment

  • Red Hat OpenStack Platform 16

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In