1438606 - OCC configured hardware is not picking up manifest changes

Status: RESOLVED INVALID

(Infrastructure & Operations :: RelOps: OpenCloudConfig, task)

Description

[Mark Cornmesser [:markco]]

This landed in the occ repo (with formatting error fixed shortly after):
https://github.com/mozilla-releng/OpenCloudConfig/commit/52b59242fd02e24c705c9960700b2beff7e227ab#diff-08fd04da1b9c3e4c1c9ab1fe42494a35

If the machine is newly deployed the or if the rundsc.ps1 command is ran manual the package is installed. However, if rundsc.ps1 is ran as a the schedule task after start up, it does not install. It appears that it checks the manifest as it was during the first run. C:\log has new logs for the existing packages, but no log for the new package or the dsc run.

Comment 1

[Mark Cornmesser [:markco]]

Grenade: Any ideas?

Comment 2

[Rob Thijssen [:grenade (EET/UTC+0300)]]

i suspect that the scheduled task may not be firing.
when $runDscOnWorker is set (it is for hardware), dsc itself (not occ) keeps the compiled mof from the last dsc run in the dsc cache (C:\Windows\System32\Configuration\*.mof). If the scheduled task runs it would delete the cache and do a fresh occ and dsc run. However, if for some reason the scheduled task is not triggered, the dsc run that occurs is actually the cached mof file from the last dsc run.
i would check the scheduled task and see if it's somehow broken or complaining of a syntax error or some other problem.

Comment 3

[Mark Cornmesser [:markco]]

This a permission issues on C:\Windows\System32\Configuration\*.mof

Comment 4

[Mark Cornmesser [:markco]]

This is not a permissions issue. It will eventually pick up and apply the changes in the manifest. However, I don't know how long it takes. There also seems that a small percentage doesn't pickup changes. I am going to look into having a schedule task clearing the dsc cache periodically or something that would have the same affect.

Comment 5

[ablew]

backlog cleanup, no longer needed.