Open eehret opened 1 year ago
I had to revise the description above because I realized I wasn't correctly framing the issue; the file in question actually does exist at the time of compliance check
Hi @eehret, could you share with us the properties of that file as well please?
@gaelcolas Here you go... happy to provide this a different way if needed:
[azops.eric.ehret@022gc.onmicrosoft.com@vm-azam-rhel7-b ~]$ ls -la /etc/cron.deny
-rw-------. 1 root root 0 Nov 30 2021 /etc/cron.deny
Thanks for your help!
Hi @eehret, we are looking into the root cause of this issue. Will get back to you.
Details of the scenario you tried and the problem that is occurring
I have an nxFile resource in which I'm trying to ensure a specific file does not exist.
It's crashing on my test system and the node fails to report compliance for any of the items in the same configuration.
Verbose logs showing the problem
Suggested solution to the issue
Unsure, I don't have the luxury of time to trace through the source code to find the problem. It seems to be running code related to determining its access mode / file attributes, so maybe there's a problem there. Note that I am not setting the Mode attribute on the nxFile resource because it's irrelevant. The file should not exist, regardless of any mode it might have had.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
[root@vm-azam-rhel7-b azops.eric.ehret]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.9 (Maipo) [root@vm-azam-rhel7-b azops.eric.ehret]# uname -r 3.10.0-1160.88.1.el7.x86_64
Version and build of PowerShell the target node is running
7.3.6
Version of the DSC module that was used
1.2.0