Issue in setting up cpu pinning/hugepages

Issue

• When we applied the configuration ( CPU pinning / huge pages for our SRIOV workers ), a node keep rebooting in a loop.
• Currently, we are trying to apply this config on two nodes only. These two nodes have different number of CPU's

Worker 1:- 
NUMA node0 CPU(s):   0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60,62,64,66,68,70,72,74,76,78,80,82,84,86
NUMA node1 CPU(s):   1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59,61,63,65,67,69,71,73,75,77,79,81,83,85,87

Worker 2:- 
NUMA node0 CPU(s):   0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60,62,64,66,68,70,72,74,76,78
NUMA node1 CPU(s):   1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59,61,63,65,67,69,71,73,75,77,79

• A performance profile like this would cause any trouble especially when both the nodes have different CPU specifications?

=== Performance Profile ===
apiVersion: performance.openshift.io/v1
kind: PerformanceProfile
metadata:
  name: performance-sriov
spec:
  cpu:
    isolated: 0,2,4,6,8,10,12,14,16
    reserved: 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59,61,63,65,67,69,71,73,75,77,79
  hugepages:
    defaultHugepagesSize: 1G
    pages:
      - count: 70
        size: 1G
  nodeSelector:
    node-role.kubernetes.io/with-sriov: ""
  numa:
    topologyPolicy: "single-numa-node"
  realTimeKernel:
    enabled: false