clones don't show identification numbers after update (PACEMAKER COROSYNC)

This document (7015095) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise High Availability Extension 11 Service Pack 3

Situation

Before an update to SLES 11 SP3 HAE a crm_mon output might have looked like

Clone Set: base_clone [test_group]
     Resource Group: test_group:0
         test1:0        (ocf::heartbeat:Dummy): Started baubas
         test2:0        (ocf::heartbeat:Dummy): Stopped

but after the update the output looks like

Clone Set: base_clone [test_group]
     Resource Group: test_group:0
         test1        (ocf::heartbeat:Dummy): Started baubas
         test2        (ocf::heartbeat:Dummy): Stopped

which is seemingly missing the :0 and :1 elements that were visible before.

Resolution

This is intentional, as the default setting of a clone is to be globally-unique="false" which makes every instance of a clone anonymous.

If for any reason it is needed to have the numbers, then the clone has to be reconfigured to be globally-unique="true" so for example:

clone base_clone test_group \
        meta interleave="true" globally-unique="true"

the output will then be

Clone Set: base_clone [test_group] (unique)
     Resource Group: test_group:0
         test1:0        (ocf::heartbeat:Dummy): Started baubas
         test2:0        (ocf::heartbeat:Dummy): Stopped

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.