Template auto-association with OS

Hi !
I encountered a problem with Foreman, a host was provisioned with CentOS 7.4 and after a yum update a new version has been pushed to Foreman CentOS 7.5. Now when I want to edit the host in Foreman interface there is a problem because the OS have no provisionning template and no partition table. Is there a way to tell Foreman that every new CentOS saved must use those templates and partition table ?
Thank you for your help.

This has been an issue for a while, and sadly there’s direct no solution that I’m aware of.

That said, with a bit of a workflow change, you can do something similar. The Foreman Templates plugin can associate templates using metadata in the template header (e.g. this entry). Re-importing the templates using the plugin after the new OS has been created should result in what you want, I think.

1 Like

Thank you for your reply. Sadly I expected that. It’s a good idea to reimport templates each time there is a new OS. Do you know if it exists kind of webhook to detect new OS ?