Closed UtahDave closed 1 year ago
Thanks for the fix! When should we expect this to show up in the file downloaded from winbootstrap.saltproject.io ? Is there some kind of release process for that?
https://github.com/saltstack/salt-bootstrap/releases/tag/v2023.08.03 It should be there now
Description of Issue/Question
The Windows bootstrap script defaults the RootDir to c:\salt. If c:\salt exists, then the minion continues to use c:\salt for everything, which is confusing because the minion configs should all be in the ProgramData directory now.
The bootstrap script creates all the files under c:\salt
Setup
I installed the 3006.1 Salt minion on a Windows 2016 server using the bootstrap script available at https://winbootstrap.saltproject.io/. The only config changed was the "master" option pointing to my master.
Steps to Reproduce Issue
use
grains.set
to set a grain and then you'll find the grains file in c:\salt\conf\grains You'll also see all the other config files will be found in c:\salt as well.If you do a fresh install of Salt 3006.1 on Windows and DO NOT use the bootstrap script, but use the installer exe itself, you'll find that everything is configured to use
c:\ProgramData\Salt Project\Salt\conf
. The grains file will be created in that directory as expected.I'm guessing that vRA / Aria Automation is using the bootstrap script when configuring new VMs, which is causing the problems to show up. I could be wrong on that, but that's my best guess.
Versions and Systems
The latest bootstrap script for windows from https://winbootstrap.saltproject.io/