OpenStack update on controller fails with puppet trying to re-add node to PaceMaker cluster

Solution Verified - Updated -

Issue

When running openstack overcloud update Controller run, the playbook fails with this error:

Aug 18 03:28:24 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 addr=192.168.1.103 to Cluster tripleo_cluster]/returns: Error: Node name 'controller-1' is already used by existing nodes; please, use other name\n<13>Aug 18 03:28:24 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 addr=192.168.1.103 to Cluster tripleo_cluster]/returns: Error: Node address '192.168.1.103' is already used by existing nodes; please, use other address\n<13>Aug 18 03:28:24 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 addr=192.168.1.103 to Cluster tripleo_cluster]/returns: Error: controller-1: Running cluster services: 'corosync', 'pacemaker', the host seems to be in a cluster already, use --force to override\n<13>Aug 18 03:28:24 puppet-user: Notice: /Stage[main]/Pacemaker::Corosync/Exec[Adding Cluster node: controller-1 addr=192.168.1.103 to Cluster tripleo_cluster]/returns: Error: controller-1: Cluster configuration files found, the host seems to be in a cluster already, use --force to override

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