Actually it seems that ```crm resource show #{resource}``` would require the name of the clone (instead of the underlying primitive). If that is true we would be again having a naming problem with clones of groups. At least on my setup I see this:

Excerpt of crm configure show:
```
primitive openstack-neutron lsb:openstack-neutron \
        op monitor interval="10s"
clone clone-openstack-neutron openstack-neutron
```

Output of ```crm resource status openstack-neutron```:
```resource openstack-neutron is running on: d52-54-00-a7-7f-ae```

Even though openstack-neutron is definitely running on all cluster nodes.

```crm resource status clone-openstack-neutron``` gives this:

```
resource clone-openstack-neutron is running on: d52-54-00-a7-7f-ae 
resource clone-openstack-neutron is running on: d52-54-00-f6-96-5e 
```

One more reason to use ```service #{new_resource.service_name} status```