Operator cannot move pod, in case of using node_readiness_label

Hello.

What is a problem

Operator not able to move pod when node_readiness_label was deleted from k8s node and this node was cordoned.

time="2020-01-14T14:38:32Z" level=warning msg="failed to move master pods from the node \"test-k8s-worker-2\": timeout of 0s minutes expired" pkg=controller

What is my ENV

Part of OperatorConfiguration:

apiVersion: "acid.zalan.do/v1"
kind: OperatorConfiguration
metadata:
  name: postgresql-operator-configuration
configuration:
  etcd_host: ""
  docker_image: registry.opensource.zalan.do/acid/spilo-11:1.6-p1
.....................................................................
    node_readiness_label:
      lifecycle-status: ready

Postgres Operator image registry.opensource.zalan.do/acid/postgres-operator:v1.3.0

That is how configured workers, as you can see one of them cordoned and does not have appropriate label

test-k8s-worker-1   Ready                      <none>   92d   v1.13.5   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ceph-role=worker,kubernetes.io/hostname=test-k8s-worker-1,lifecycle-status=ready
test-k8s-worker-2   Ready,SchedulingDisabled   <none>   92d   v1.13.5   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ceph-role=worker,kubernetes.io/hostname=test-k8s-worker-2
test-k8s-worker-3   Ready                      <none>   92d   v1.13.5   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,ceph-role=worker,kubernetes.io/hostname=test-k8s-worker-3,lifecycle-status=ready

Pods:

grafana-acid-postgres-0                     2/2     Running     0          176m    10.233.81.7    test-k8s-worker-3   <none>           <none>
grafana-acid-postgres-1                     2/2     Running     0          176m    10.233.64.10   test-k8s-worker-2   <none>           <none>```


### What I want to achieve

It will be good if operator was able to reschedule pod from unlabeled and cordoned , to another k8s node

Start in the controller path indicated by the warning and trace how node_readiness_label is used when a node is cordoned or loses its label. Reproduce the configuration with an unlabeled, cordoned node and verify that the affected PostgreSQL pod is rescheduled to an eligible node.