Open alan-cugler opened 4 years ago
Thanks for the report. There might be some other options to get the master config file to pass along, or maybe it's being lost in translation and only the minion file makes it over. Have you tried not sending the minion config file and only sending the master config file to see if shows up modified?
I think that's what is happening here, unless I'm ready it totally wrong.
I have tried removing the minion configs and just passing through -opts
the master config options. That didnt give any different results for the master.
Gotcha, I'll see if anyone on @saltstack/team-core has some suggestions as I'm not super familiar with this area of salt...
Description of Issue
I am spinning up a vm on digitalocean. The vm is to have a minion and master process running on it upon completed provisioning. The minion options populate but not the master.
I am using Orchestration with a
salt.runner
for thecloud.profile
module.Setup
provider file for credentials to digitalocean
profile file for hypervisor provisioning options for the vm
orchestration state
master_spinup: salt.runner:
The orchestration state runs perfectly, I ssh into the vm and the minions config file (/etc/salt/minion) contains the changes, but the masters configuration file (/etc/salt/master) is still the default configuration file. Both processes are running successfully as well.
I have also attempted setting the master option in the orchestration file on
- kwarg:
as well. this resulted the same.Versions Report