Comment 50 for bug 1829403

Hi Tao, Thanks a lot your help to investigating.
   This time issue was not same as 2019-05-09 peng found , which db data is correct.
But I think your analysis was perhaps right.

from controller-0 sysinv.log.1
compute-1:
2019-07-19 20:49:38.371 compute-1 ihost check_unlock_worker
2019-07-19 20:49:42.437 Updating hiera for host: compute-1 with config_uuid
from compute-1 agent schedule is around
20:39:27.891 every one minutes. it was not between 38s to 42s.

compute-0:
2019-07-19 20:50:00.666 compute-0 ihost check_unlock_worker
2019-07-19 20:50:05.532 Updating hiera for host: compute-0 with config_uuid: None
from compute-0 agent schedule is around
20:37:00.718 every one minutes. it was between 00s to 05s.

compute-2:
019-07-19 20:49:47.163 compute-2 ihost check_unlock_worker
2019-07-19 20:49:50.612 Updating hiera for host: compute-2 with config_uuid: None
from compute-0 agent schedule is around
20:44:47.016 every one minutes, os it was between 47s to 50s

I made a change to ingore agent mem report when unlocking. you can review it
Thanks.