minion defaults to saltenv base

[Brian Glogower]

Hi,

I am trying to get salt running with one master and a test minion. I have used bootstrap_salt.sh to install 2016.3.2 on both servers. The master is using gitfs with two branches, master (base) and stage. The problem that I am seeing is that running salt-call from the minion or salt from the master in debug/trace mode reveals that saltenv is being set to base and the minion never bothers to look at the stage environment in the top file. This causes 'No Top file or external nodes data matches found.', since I am filter targets with help from grains, causing the minion to not match any of the targets in the base environment specified in top.sls.

I know you can specify saltenv on the cli for both salt-call and salt or set environment in the minion's config, but from what I have read, that is not best practice (I believe):

• https://docs.saltstack.com/en/latest/ref/states/top.html#choosing-an-environment-to-target
  
• minion config:
• # Normally, the minion is not isolated to any single environment on the master
• # when running states, but the environment can be isolated on the minion side
• # by statically setting it. Remember that the recommended way to manage
• # environments is to isolate via the top file.
• # environment: None

Am I missing something?

Thanks,

Brian

[Brian Glogower]

Looks like I might be hitting https://github.com/saltstack/salt/issues/35045 which also references https://github.com/saltstack/salt/issues/30434