Bug #18785
Updated by Ward Vandewege about 2 years ago
On the 2.3-release branch, tip (commit:d09550506dbd31b92e53b4e861924e49027acabb), when configuring a single host single hostname with Let's Encrypt enabled:
<pre>
Setting up salt-minion (3004+ds-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/salt-minion.service → /lib/systemd/system/salt-minion.service.
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
* INFO: Salt installed!
Synchronizing state of salt-minion.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable salt-minion
Removed /etc/systemd/system/multi-user.target.wants/salt-minion.service.
Cloning formulas
Writing pillars and states
sed: can't read /srv/pillars/nginx_download_configuration.sls: No such file or directory
sed: can't read /srv/pillars/nginx_collections_configuration.sls: No such file or directory
[ERROR ] Specified SLS 'aws_credentials' in environment 'base' is not available on the salt master
[ERROR ] Template was specified incorrectly: False
[ERROR ] Specified SLS 'letsencrypt' in environment 'base' is not available on the salt master
[ERROR ] Template was specified incorrectly: False
[CRITICAL] Pillar render error: Specified SLS 'aws_credentials' in environment 'base' is not available on the salt master
[CRITICAL] Pillar render error: Specified SLS 'letsencrypt' in environment 'base' is not available on the salt master
[INFO ] Loading fresh modules for state activity
local:
Data failed to compile:
----------
Pillar failed to render with the following messages:
----------
Specified SLS 'aws_credentials' in environment 'base' is not available on the salt master
----------
Specified SLS 'letsencrypt' in environment 'base' is not available on the salt master
Removing .psql file
</pre>