'pcs resource move' prevents a resource from failing back to its original node later

Issue

• After using pcs resource move, a resource will not failback to its original location if it eventually fails or the node its running on fails.
• pcs resource move seems to ban the node its running on.
• pcs resource move resource-id command prevents the resource from moving back on the cluster node. For example, when a resource is moved from cluster node1 to node2 manually, then the resource fails to start on node1 when it is failed over again from node2. The resource is seen in the stopped state on node1.
• Red Hat Cluster created a contraint with score of -INFINITY when I tried to move services