search

PowerShell / PSDscResources

MIT License
129 stars 53 forks source link

Environment: Variable not recognised until after reboot #122

Open OffColour opened 5 years ago

OffColour commented 5 years ago

DSC setting:

Environment RabbitMQ_Base { Name = 'RABBITMQ_BASE' Value = 'F:\RABBITMQ' Ensure = 'Present' Path = $false Target = @('Process', 'Machine') }

Azure DSC reports not compliant until after the server has been rebooted.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

PlagueHO commented 5 years ago

Thanks for raising this @OffColour

If you log into the machine after DSC has been applied but before the machine has been rebooted and open a PowerShell (or CMD) console, does the RABBITMQ_BASE environment variable exist?

I've used this resource for a number of different configs in non-Azure VM's and the environment variable is always available to any following config step. Have you possibly your Rabbit MQ config in a non-Azure VM and if so, did it exhibit the same problem?

OffColour commented 5 years ago

@PlagueHO Apologies for not being clear. Yes, the variable exists and is used correctly by subsequent steps before a reboot so possibly an issue with the Azure DSC extension not picking up the change and hence not reporting it back to the Automation account properly.

I've not got any non-Azure based VMs or DSC setup to to test this with.