Description of problem:
autofencing didn't configure fencing on nodes with pacemaker_remote in composable roles environment. 

[stack@puma33 ~]$ openstack overcloud generate fencing -a reboot --ipmi-lanplus --ipmi-level administrator instackenv.json
parameter_defaults:
  EnableFencing: true
  FencingConfig:
    devices:
    - agent: fence_ipmilan
      host_mac: 44:1e:a1:73:39:91
      params:
        action: reboot
        ipaddr: 10.35.160.18
        lanplus: true
        login: admin
        passwd: admin
        pcmk_host_list: puma04
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 44:1e:a1:73:3d:43
      params:
        action: reboot
        ipaddr: 10.35.160.20
        lanplus: true
        login: admin
        passwd: admin
        pcmk_host_list: puma05
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 44:1e:a1:73:36:6b
      params:
        action: reboot
        ipaddr: 10.35.160.78
        lanplus: true
        login: admin
        passwd: admin
        pcmk_host_list: puma34
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 44:1e:a1:73:38:5f
      params:
        action: reboot
        ipaddr: 10.35.160.90
        lanplus: true
        login: admin
        passwd: admin
        pcmk_host_list: puma40
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 44:1e:a1:71:a7:45
      params:
        action: reboot
        ipaddr: 10.35.160.38
        lanplus: true
        login: admin
        passwd: admin
        pcmk_host_list: puma14
        privlvl: administrator
    - agent: fence_ipmilan
      host_mac: 44:1e:a1:71:a6:37
      params:
        action: reboot
        ipaddr: 10.35.160.42
        lanplus: true
        login: admin
        passwd: admin
        pcmk_host_list: puma16
        privlvl: administrator

[stack@puma33 ~]$ 
[root@puma04 ~]# pcs status
Cluster name: tripleo_cluster
Stack: corosync
Current DC: puma04 (version 1.1.15-11.el7_3.4-e174ec8) - partition with quorum
Last updated: Sun Apr 23 11:24:20 2017		Last change: Sun Apr 23 11:21:49 2017 by root via cibadmin on puma34

6 nodes and 37 resources configured

Online: [ puma04 puma05 puma34 ]
RemoteOnline: [ puma14 puma16 puma40 ]

Full list of resources:

 puma14	(ocf::pacemaker:remote):	Started puma04
 puma16	(ocf::pacemaker:remote):	Started puma05
 puma40	(ocf::pacemaker:remote):	Started puma34
 Master/Slave Set: galera-master [galera]
     Masters: [ puma14 puma16 puma40 ]
     Stopped: [ puma04 puma05 puma34 ]
 Master/Slave Set: redis-master [redis]
     Masters: [ puma34 ]
     Slaves: [ puma04 puma05 ]
     Stopped: [ puma14 puma16 puma40 ]
 Clone Set: rabbitmq-clone [rabbitmq]
     Started: [ puma04 puma05 puma34 ]
     Stopped: [ puma14 puma16 puma40 ]
 ip-192.168.24.11	(ocf::heartbeat:IPaddr2):	Started puma04
 ip-10.35.180.17	(ocf::heartbeat:IPaddr2):	Started puma05
 ip-172.17.0.17	(ocf::heartbeat:IPaddr2):	Started puma34
 ip-172.17.0.16	(ocf::heartbeat:IPaddr2):	Started puma04
 ip-172.18.0.11	(ocf::heartbeat:IPaddr2):	Started puma05
 ip-172.19.0.17	(ocf::heartbeat:IPaddr2):	Started puma34
 Clone Set: haproxy-clone [haproxy]
     Started: [ puma04 puma05 puma34 ]
     Stopped: [ puma14 puma16 puma40 ]
 openstack-cinder-volume	(systemd:openstack-cinder-volume):	Started puma04
 stonith-fence_ipmilan-441ea173366b	(stonith:fence_ipmilan):	Started puma05
 stonith-fence_ipmilan-441ea1733d43	(stonith:fence_ipmilan):	Started puma34
 stonith-fence_ipmilan-441ea1733991	(stonith:fence_ipmilan):	Started puma05

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
[root@puma04 ~]# pcs stonith show stonith-fence_ipmilan-441ea173366b
 Resource: stonith-fence_ipmilan-441ea173366b (class=stonith type=fence_ipmilan)
  Attributes: pcmk_host_list=puma34 ipaddr=10.35.160.78 passwd=admin lanplus=true login=admin action=reboot privlvl=administrator
  Operations: monitor interval=60s (stonith-fence_ipmilan-441ea173366b-monitor-interval-60s)
[root@puma04 ~]# pcs stonith show stonith-fence_ipmilan-441ea1733d43
 Resource: stonith-fence_ipmilan-441ea1733d43 (class=stonith type=fence_ipmilan)
  Attributes: pcmk_host_list=puma05 ipaddr=10.35.160.20 passwd=admin lanplus=true login=admin action=reboot privlvl=administrator
  Operations: monitor interval=60s (stonith-fence_ipmilan-441ea1733d43-monitor-interval-60s)
[root@puma04 ~]# pcs stonith show stonith-fence_ipmilan-441ea1733991
 Resource: stonith-fence_ipmilan-441ea1733991 (class=stonith type=fence_ipmilan)
  Attributes: pcmk_host_list=puma04 ipaddr=10.35.160.18 passwd=admin lanplus=true login=admin action=reboot privlvl=administrator
  Operations: monitor interval=60s (stonith-fence_ipmilan-441ea1733991-monitor-interval-60s)
[root@puma04 ~]# 

roles_data.yaml 
- name: Galera
  HostnameFormatDefault: '%stackname%-galera-%index%'
  ServicesDefault:
    - OS::TripleO::Services::CACerts
    - OS::TripleO::Services::Timezone
    - OS::TripleO::Services::Ntp
    - OS::TripleO::Services::Snmp
    - OS::TripleO::Services::Kernel
    - OS::TripleO::Services::PacemakerRemote
    - OS::TripleO::Services::MySQL
    - OS::TripleO::Services::TripleoPackages
    - OS::TripleO::Services::TripleoFirewall
    - OS::TripleO::Services::SensuClient
    - OS::TripleO::Services::FluentdClient


Steps to Reproduce:
1. deploy composable roles environment and assign the pacemaker_remote to a role
2. use openstack overcloud generate fencing command and verify all hosts with pacemaker/pacemaker_remote are present.
3. $DEPLOY -e generate_fencing_output.yml
4. log into one of the controllers and check theat the installation confgured fencing to each node which have pacemaker/pacemaker_remote it is role.

Actual results:
autofencing configured fencing only to hosts with OS::TripleO::Services::Pacemaker


Expected results:
autofencing should be configured also to nodes with OS::TripleO::Services::PacemakerRemote