So the BLAdmin ROLE has the default object permission template of ‘Windows-ACL’ and that is what you expect to have been applied on the created folder ?
The role that runs the job, does that role have the default opt of ‘Linux-ACL’ by chance ?
we took a look at the role but couldn't find any part of the linux-acl.
I have recreated the acl-template and the acl-policy and added it back to the role.
The result was nearly the same but this time we recognized a new error in the provisioning logs -
a part of a path was missing. Somehow we lost the permission of the windows-acl on two systemobject instances.
One in the Custom Property Class, this one was responsible for the missing/wrong path.
The other one was the PXE Datastore Instance for Windows. (that one had nothing to do with the reported issue)
Problem is solved and it looks like everything else is working fine now.
btw.: 8.9 also solved our problem with provisioning SLES server while using the 8.8 agent.
Kind regards and a happy new year