In pcs status, what does the DISABLED resource count mean?

Issue

When disabling a resource in pacemaker, pcs status can often show more resources disabled in the status. It can also occur when resources have failures in Failed Actions of pcs status.

[root@nodename ~]# pcs status

Cluster name: mycluster
Stack: corosync
Current DC: node2 (version 1.1.15-11.el7_3.4-e174ec8) - partition with quorum
Last updated: Mon Jun  5 15:17:41 2017          Last change: Mon Jun  5 14:18:25 2017 by root via crm_attribute on node1

2 nodes and 63 resources configured: 2 resources DISABLED and 0 BLOCKED from being started due to failures

Online: [ node1 node2 ]

Full list of resources:

 fence_node1      (stonith:fence_ipmilan):        Started node2
 fence_node2      (stonith:fence_ipmilan):        Started node1
 Resource Group: nlslb1
     ClusterIP  (ocf::heartbeat:IPaddr2):       Started node1
     db_home_vg (ocf::heartbeat:LVM):   Started node1
     db_catalog_vg      (ocf::heartbeat:LVM):   Started node1
     db_data_vg (ocf::heartbeat:LVM):   Started node1
     db_temp_vg (ocf::heartbeat:LVM):   Started node1
     db_backup_vg       (ocf::heartbeat:LVM):   Started node1
     SAPIQ_siqlp1       (ocf::heartbeat:Filesystem):    Started node1
     SAPIQ_LP1  (ocf::heartbeat:Filesystem):    Started node1
     sapiq_rhel_ha      (lsb:sapiq_rhel_ha):    Stopped (disabled)

Failed Actions:
* sapiq_rhel_ha_monitor_0 on node1 'not installed' (5): call=260, status=Not installed, exitreason='none',
    last-rc-change='Mon Jun  5 15:07:55 2017', queued=0ms, exec=0ms
* sapiq_rhel_ha_monitor_0 on node2 'not installed' (5): call=254, status=Not installed, exitreason='none',
    last-rc-change='Mon Jun  5 15:07:52 2017', queued=0ms, exec=0ms


Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
[root@nodename ~]#