Red Hat Bugzilla – Bug 862235
kickstart snippets added/changed on disk do not always take effect
Last modified: 2018-02-05 19:41:31 EST
Description of problem:
Adding a custom sinppet will not take affect
Version-Release number of selected component (if applicable):
always (for a provisioned job)
Steps to Reproduce:
1. Add snippet that overrides installed snippet
2. add job to scheduler that uses snippet
new snippet is not used
I guess we're expecting it to be.
We could add cache=None to the the SandboxedEnvironment constructor.
I think jinja should be able to do this unless there is a good reason not to, I think the current behvaiour is unexpected.
by cache=None, I of course mean 'cache_size=0'.To be clear, the snippet will take affect if the process (beakerd in this case) is restarted.
I've also filed an upstream bug for this.
On Gerrit: http://gerrit.beaker-project.org/1458
Verified by creating /etc/beaker/snippets/network with the following contents:
#dummy network configuration
This line is included in the generated kickstart file, instead of the usually found:
# no specific network configuration
This has now been released