/sys/fs/cgroup/cpuset/machine.slice/machine-qemu\\x2d4\\x2dinstance\\x2d00000021.scope/emulator/cpuset.cpus': Permission denied

Issue

• Trying to create an instance. Getting the following error:

20-05-11 08:43:43.437 28 ERROR nova.scheduler.utils 
[req-3eb6a738-f61c-4876-81f8-796e25ac3aed a0eaf04e8f5e4d4a9ec64f9bde40ec28 1d6d9fd1f5624118ae7c00258327d8e0 - default default] 
[instance: 06ad309f-97f3-403a-8994-f535c4cd780b] 
Error from last host: thomas96-hpcomputesriov-sfr-0.localdomain (node thomas96-hpcomputesriov-sfr-0.localdomain): 
[u'Traceback (most recent call last):\n', u'  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2008, in _do_build_and_run_instance\n    
filter_properties, request_spec)\n', 
u'  File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2292, in _build_and_run_instance\n    
instance_uuid=instance.uuid, reason=six.text_type(e))\n', 
u"RescheduledException: Build of instance 06ad309f-97f3-403a-8994-f535c4cd780b was re-scheduled: 
Unable to write to '/sys/fs/cgroup/cpuset/machine.slice/machine-qemu\\x2d4\\x2dinstance\\x2d00000021.scope/emulator/cpuset.cpus': Permission denied\n"]

• This was all running just fine previous to a upgrade that was done in early march … Additional information is that this is only an issue when attempting to deploy instances to nodes that are configured for SR-IOV and pinned cores. When deploying to other compute nodes where the instance is not pinned and not needing SR-IOV all works well …