The preview has been generated for that exact failing host.
Expected outcome:
Host receives valid JSON and proceeds per received key values. Foreman and Proxy versions:
Foreman 1.21 + Smart Proxy 1.21 Foreman and Proxy plugin versions:
Discovery 14.0.1 + Discovery Image 3.5.0 Other relevant data:
Both template and snippet have been imported to Foreman using foreman_templates plugin.
I tried to hand-create another snippet and use it within the template, same result.
Maybe I should update Discovery image to version 3.5.1? Gonna try that…
Same exact template/snippet working no problem with Foreman 1.19 + Discovery 13.0.1
Hello, thanks for good info. I have tested this on develop branch and it works fine. We have been redesigning template renderer during 1.20 and 1.21 and it is possible this is a regression. However I am unable to tell which change fixed it.
This has nothing to do with FDI, it’s something in Foreman app. Usually this is a problem with taxonomy, when a resource is not in the same organization or location as the host. Can you check that the location which is not assigned is not by chance assigned to the host you provision? This must always match otherwise the symptom is “not found” as our filtering stack never returns it.
@TimoGoebel do you think that this might be related to the snippet bug for StringTemplate you recently fixed? This is my only idea, out of anything else.
Yeah, Source::String does not allow any snippet rendering. If we want to allow snippets inside kexec templates (which I believe we want), we’d need to change these lines to
render_template(template: template)
So this should be an easy fix. I don’t have time to open a PR this week, but I’ll add it to my list.
