You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
If attempting to sync a custom renderer when that renderer is already in the render pipeline via the renderer configuration options, the operation will fail with the following error:
salt.exceptions.LoaderError: The renderer some_custom_thing|jinja|yaml is unavailable, this error is often because the needed software is unavailable
This creates a "chicken and egg" scenario where the minion configuration needs to be temporarily modified until after the custom renderer has been synced.
Expected behavior
When specifying a renderer that doesn't exist (or doesn't exist yet), we should fall back to the default renderer much like we do when a non-existent outputter is specified:
root@u22-party-01:~# salt-call test.ping --output some_custom_thing
[ERROR ] Invalid outputter some_custom_thing specified, fall back to nested
local:
True
This would allow the saltutil.sync_renderers execution to run successfully and sync any custom renderers that might be configured.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
Salt Version:
Salt: 3007.0Python Version:
Python: 3.10.13 (main, Feb 19 2024, 03:31:20) [GCC 11.2.0]Dependency Versions:
cffi: 1.16.0cherrypy: 18.8.0dateutil: 2.8.2docker-py: Not Installedgitdb: Not Installedgitpython: Not InstalledJinja2: 3.1.3libgit2: Not Installedlooseversion: 1.3.0M2Crypto: Not InstalledMako: Not Installedmsgpack: 1.0.7msgpack-pure: Not Installedmysql-python: Not Installedpackaging: 23.1pycparser: 2.21pycrypto: Not Installedpycryptodome: 3.19.1pygit2: Not Installedpython-gnupg: 0.5.2PyYAML: 6.0.1PyZMQ: 25.1.2relenv: 0.15.1smmap: Not Installedtimelib: 0.3.0Tornado: 6.3.3ZMQ: 4.3.4Salt Extensions:
saltext.prometheus: 2.0.3saltext.vmware: 23.6.29.0rc1Salt Package Information:
Package Type: onedirSystem Versions:
dist: ubuntu 22.04.4 jammylocale: utf-8machine: x86_64release: 5.15.0-101-genericsystem: Linuxversion: Ubuntu 22.04.4 jammy
The text was updated successfully, but these errors were encountered:
Description
If attempting to sync a custom renderer when that renderer is already in the render pipeline via the
renderer
configuration options, the operation will fail with the following error:This creates a "chicken and egg" scenario where the minion configuration needs to be temporarily modified until after the custom renderer has been synced.
Steps to Reproduce the behavior
Expected behavior
When specifying a renderer that doesn't exist (or doesn't exist yet), we should fall back to the default renderer much like we do when a non-existent outputter is specified:
This would allow the
saltutil.sync_renderers
execution to run successfully and sync any custom renderers that might be configured.Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)The text was updated successfully, but these errors were encountered: