Replacement of the first controller node fails at step 1 if the same hostname is used for a new node

Solution Verified - Updated -

Issue

  • When replacing the first controller node by a new node with the same hostname, deployment fails at step 1 because of the following error.

    Dec 10 12:34:56 puppet-user: Error: '/sbin/pcs cluster setup tripleo_cluster controller-0 addr=192.168.0.10 controller-1 addr=192.168.0.11 controller-2 addr=192.168.0.12' returned 1 instead of one of [0]
    Dec 10 12:34:56 puppet-user: Error: /Stage[main]/Pacemaker::Corosync/Exec[Create Cluster tripleo_cluster]/returns: change from 'notrun' to ['0'] failed: '/sbin/pcs cluster setup tripleo_cluster controller-0 addr=192.168.0.10 controller-1 addr=192.168.0.11 controller-2 addr=192.168.0.12' returned 1 instead of one of [0]
    

Environment

  • Red Hat OpenStack Platform 16.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content