Templates

Support
1

Hi,

It looks like that sometimes provisioning templates are restored to default.

I think that it's happens when I click "Build PXE Default".
Is it by design?

Thanks!
Ido

2

Hi Marek,

Thank you for the follow up.
Let me please try to make sure that I understand.
If template is locked, is it means that no updates will happen to the
template on any trigger (upgrade, foreman-installer, etc') that will occur?

Thanks!
Ido

··· On Tuesday, September 26, 2017 at 9:35:32 AM UTC+3, Ido Kaplan wrote: > > Hi, > > It looks like that sometimes provisioning templates are restored to > default. > > I think that it's happens when I click "Build PXE Default". > Is it by design? > > Thanks! > Ido >
3

> Hi,
>
> It looks like that sometimes provisioning templates are restored to
> default.

Can you clarify what you mean here? Are the contents of the templates
in Foreman changing, or on the TFTP proxy?

> I think that it's happens when I click "Build PXE Default".
> Is it by design?

When that button is clicked, all the TFTP proxies should have the
$tftpdir/pxelinux.cfg/default file rewritten to match the selected
default template. Nothing should change in Foreman, or in any other
tftp file.

Greg

··· On Mon, 2017-09-25 at 23:35 -0700, Ido Kaplan wrote:
4

Hi Greg,

I mean about contents of the templates in Foreman, for example - "Kickstart
default.rb"?

··· On Tue, Sep 26, 2017 at 12:54 PM, Greg Sutcliffe wrote:

On Mon, 2017-09-25 at 23:35 -0700, Ido Kaplan wrote:

Hi,

It looks like that sometimes provisioning templates are restored to
default.

Can you clarify what you mean here? Are the contents of the templates
in Foreman changing, or on the TFTP proxy?

I think that it’s happens when I click “Build PXE Default”.
Is it by design?

When that button is clicked, all the TFTP proxies should have the
$tftpdir/pxelinux.cfg/default file rewritten to match the selected
default template. Nothing should change in Foreman, or in any other
tftp file.

Greg

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/03QXstOUeQ8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

5

Hello Ido,

no it's not what locked means. When template is locked, it can't be edited by
users. User need to unlock them first, which gives them a warning about the
template content can be overridden.

Hope that helps

··· -- Marek

On úterý 26. září 2017 16:08:03 CEST Ido Kaplan wrote:

Hi Marek,

Thank you for the follow up.
Let me please try to make sure that I understand.
If template is locked, is it means that no updates will happen to the
template on any trigger (upgrade, foreman-installer, etc’) that will occur?

Thanks!
Ido

On Tuesday, September 26, 2017 at 9:35:32 AM UTC+3, Ido Kaplan wrote:

Hi,

It looks like that sometimes provisioning templates are restored to
default.

I think that it’s happens when I click “Build PXE Default”.
Is it by design?

Thanks!
Ido

6

Those should not be altered by that button, no. The only time the
default templates would be updated would be during a version upgrade of
Foreman.

Changes to templates are audited, so you should be able to see the
history of changes, so that's worth looking at to see what might have
made the changes. Also, if you can reproduce it reliably, we can try
and see if we see the same behaviour

Greg

··· On Tue, 2017-09-26 at 13:51 +0300, Ido Kaplan wrote: > Hi Greg, > > I mean about contents of the templates in Foreman, for example - > "Kickstart default.rb"?
7

In fact anything that triggers foreman-rake db:seed changes the default
template content (Foreman 1.14+). That can be run of foreman-installer,
installing a plugin or manual trigger. These changes are not audited IIRC. If
you need to adjust template that is shipped by default, it is a good idea to
clone it first. Note that you'd miss all future updates and it's up to you to
keep it up to date. Default templates should be locked since 1.15.

··· -- Marek

On úterý 26. září 2017 13:24:21 CEST Greg Sutcliffe wrote:

On Tue, 2017-09-26 at 13:51 +0300, Ido Kaplan wrote:

Hi Greg,

I mean about contents of the templates in Foreman, for example -
“Kickstart default.rb”?

Those should not be altered by that button, no. The only time the
default templates would be updated would be during a version upgrade of
Foreman.

Changes to templates are audited, so you should be able to see the
history of changes, so that’s worth looking at to see what might have
made the changes. Also, if you can reproduce it reliably, we can try
and see if we see the same behaviour

Greg

8

If there a way that templates will not be edited by any trigger?

Ido

··· > On 26 Sep 2017, at 18:27, Marek Hulán wrote: > > Hello Ido, > > no it's not what locked means. When template is locked, it can't be edited by > users. User need to unlock them first, which gives them a warning about the > template content can be overridden. > > Hope that helps > > -- > Marek > >> On úterý 26. září 2017 16:08:03 CEST Ido Kaplan wrote: >> Hi Marek, >> >> Thank you for the follow up. >> Let me please try to make sure that I understand. >> If template is locked, is it means that no updates will happen to the >> template on any trigger (upgrade, foreman-installer, etc') that will occur? >> >> Thanks! >> Ido >> >>> On Tuesday, September 26, 2017 at 9:35:32 AM UTC+3, Ido Kaplan wrote: >>> Hi, >>> >>> It looks like that sometimes provisioning templates are restored to >>> default. >>> >>> I think that it's happens when I click "Build PXE Default". >>> Is it by design? >>> >>> Thanks! >>> Ido > >