OCS 4.X - Pod in Pending State after an upgrade due to Insufficient CPU

Issue

• After an upgrade one of the monitor pods is unable to get “Running” status due Insufficient CPU.

        Events:
          Type     Reason            Age   From               Message
          ----     ------            ----  ----               -------
          Warning  FailedScheduling  13h   default-scheduler  0/10 nodes are available: 3 node(s) didn't match pod affinity/anti-affinity, 3 node(s) didn't match pod anti-affinity rules, 3 Insufficient cpu, 6 node(s) didn't match node selector.

• Comparing the resources assigned to the nodes with the ones indicated in the Deployment Guide it’s seen the resources should be enough