Open eusebyu opened 1 year ago
I believe you've run into the same issue I noticed. If I'm right, I think you'll notice that your omid process crashes every time your DSC is running. omi version 1.6.10 or higher are incompatible with the DSCForLinux VM extension. If your OMI gets upgraded, as yours has, DSC will break due to OMI crashing.
Sadly there was a CVE in OMI that had to get patched, but it seems the DSC team didn't keep their solution compatible with OMI 1.6.10 and higher.
In our case if we downgrade OMI back to 1.6.9 (the version that ships with the current DSC solution) then it starts working again. But of course due to the CVE we can't actually operate like that....
I have already reported this problem to the product group responsible for DSCForLinux. They're working on a fix.
The DSC extension reports RHEL Vms as in progress all the time in the Automation Account.
It fails on TestDscConfiguration when trying to write to sys.stdout. For some reason it seems that sys.stdout is null (None).
/var/opt/microsoft/omsconfig/omsconfig.log
/var/opt/omi/log/dsc.log
This has worked in the past. Now suddenly it stopped working. This behavior is consistent on all newly provisioned VMs (RHEL 8). I also used a very simple nx script which just touches a file and checks if exists.
OS: RHEL 8.7 DSC: 1.2.4 OMI: 1.6.11 Python: 3.6.8
When I run /opt/microsoft/dsc/bin/ConsistencyInvoker, I am receiving a generic error: