rackm03 is created with /etc/containers/policy.json with below value---{
  "default": [
    {
      "type": "reject"
    }
  ],
Because of this image pulls were getting rejected, at the beginning Fusion build team helped with the debug and we changed it to{
  "default": [
    {
      "type": "insecureAcceptAnything"
    }
Due to this value mismatch with deployment time, whenever the nodes are rebooted mcp goes down to degradedoc get mcp
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-ea91cb740e8a0ed66bf93687ad41f317   False     True       True       3              0                   0                     3                      69d
worker   rendered-worker-7780c0ae34056a28c6a6a341afdfcb65   False     True       True       3              0                   0                     3                      69d

'Node compute-1-ru5.rackm03.mydomain.com is reporting: "unexpected on-disk
      state validating against rendered-worker-7780c0ae34056a28c6a6a341afdfcb65: content
      mismatch for file \"/etc/containers/policy.json\"", Node compute-1-ru6.rackm03.mydomain.com
      is reporting: "unexpected on-disk state validating against rendered-worker-7780c0ae34056a28c6a6a341afdfcb65:
      content mismatch for file \"/etc/containers/policy.json\"", Node compute-1-ru7.rackm03.mydomain.com
      is reporting: "unexpected on-disk state validating against rendered-worker-7780c0ae34056a28c6a6a341afdfcb65:
      content mismatch for file \"/etc/containers/policy.json\""'
    reason: 3 nodes are reporting degraded status on sync

    Seen this for rackm03
    ocp: 4.18.0-rc.6 <the cluster was handed over with ocp 4.16 have upgraded to ocp 4.18 later>

   It is observed every time nodes are restarted

    1.
    2.
    3.