selinux.module looks for module source in the base environment, not the current environment #43679
Labels
Bug
broken, incorrect, or confusing behavior
Core
relates to code central or existential to Salt
Execution-Module
P3
Priority 3
severity-medium
3rd level, incorrect or bad functionality, confusing and lacks a work around
stale
Milestone
Description of Issue/Question
Other states that take source kwargs (e.g., file.managed) will look in the current environment for those files. The selinux.module state looks in the base environment instead, which breaks state execution in multi-environment setups.
Setup
https://github.com/irtnog/salt-states/tree/development/tomcat/pwm.sls
https://github.com/irtnog/salt-states/tree/development/tomcat/files/tomcat-mysql.te
Note that in my setup, I use the base environment solely for targeting.
Steps to Reproduce Issue
Write an SELinux type enforcement module and corresponding SLS file that calls selinux.module (e.g., above), and save them to an environment other than base.
Run the SLS file in that environment (e.g.,
salt-call state.apply tomcat.pwm saltenv=development
).Versions Report
The text was updated successfully, but these errors were encountered: