InstanceHA creation fails when compute names start with digits in Red Hat OpenStack Platform 13

Solution In Progress - Updated -

Issue

InstanceHA creation fails when compute names start with digits in Red Hat OpenStack Platform 13

Pacemaker resource names cannot start with digits: "invalid resource name'123456789-compute','1' is not a valid first character for a resource name"

Unfortunately, our instance-ha resources are named exactly like the compute nodes and that leads to a deployment failure:

  deploy_stdout: ||
    ...
            "Error: pcs -f /var/lib/pacemaker/cib/puppet-cib-backup20191009-27088-34fwly create failed: Error: invalid resource name'123456789-compute','1' is not a valid first character for a resource name",
            "Error: /Stage[main]/Tripleo::Profile::Base::Pacemaker/Pacemaker::Resource::Remote[123456789-compute]/Pcmk_resource[123456789-compute]/ensure: change from absent to present failed: pcs -f /var/lib/pacemaker/cib/cib/puppet-cib-backup20191009-27088-34fwly create failed: Error: invalid resource name'123456789-compute','1' is not a valid first character for a resource name",
            "Warning: /Stage[main]/Tripleo::Profile::Base::Pacemaker/Exec[exec-wait-for-123456789-compute]: Skipping because of failed dependencies"
        ]
    }
        to retry, use: --limit @/var/lib/heat-config/heat-config/heat-config-ansible/69f32e10-2f1a-4c4c-81d7-7e512f2d2eb2_playbook.retry

Environment

Red Hat OpenStack Platform 13

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