[3.5.1] Template parsing error for build (Kickstart default iPXE)

Support
1

After upgrading from Foreman 3.5.0-0.1.rc2 to 3.5.1 I’m seeing the following error check when trying to rebuild physical and virtual hosts:

The following errors may prevent a successful build:

Templates (1)
Failure parsing Kickstart default iPXE: undefined method `interpolate_vars’ for nil:NilClass.

Trying to continue regardless results in a “Request failed with status code 500”. Any ideas on what’s happening here?

2

Package transaction of upgrade:

# sudo foremain-maintain packages update
$ sudo dnf history info 51
Transaction ID : 51
Begin time     : Tue 03 Jan 2023 11:30:00 AM EST
Begin rpmdb    : 1218:7d1502319f69924dd0fc1d901fd69d7588da5dcd
End time       : Tue 03 Jan 2023 11:30:56 AM EST (56 seconds)
End rpmdb      : 1218:24701dc477860808f20d2b34b912acb19ddd673e
User           : Mike Rochefort
Return-Code    : Success
Releasever     : 8
Command Line   : --disableplugin=foreman-protector update
Comment        : 
Packages Altered:
    Upgrade  foreman-3.5.1-1.el8.noarch                               @foreman
    Upgraded foreman-3.5.0-0.17.rc2.el8.noarch                        @@System
    Upgrade  foreman-cli-3.5.1-1.el8.noarch                           @foreman
    Upgraded foreman-cli-3.5.0-0.17.rc2.el8.noarch                    @@System
    Upgrade  foreman-debug-3.5.1-1.el8.noarch                         @foreman
    Upgraded foreman-debug-3.5.0-0.17.rc2.el8.noarch                  @@System
    Upgrade  foreman-dynflow-sidekiq-3.5.1-1.el8.noarch               @foreman
    Upgraded foreman-dynflow-sidekiq-3.5.0-0.17.rc2.el8.noarch        @@System
    Upgrade  foreman-ec2-3.5.1-1.el8.noarch                           @foreman
    Upgraded foreman-ec2-3.5.0-0.17.rc2.el8.noarch                    @@System
    Upgrade  foreman-installer-1:3.5.1-1.el8.noarch                   @foreman
    Upgraded foreman-installer-1:3.5.0-0.1.rc2.el8.noarch             @@System
    Upgrade  foreman-installer-katello-1:3.5.1-1.el8.noarch           @foreman
    Upgraded foreman-installer-katello-1:3.5.0-0.1.rc2.el8.noarch     @@System
    Upgrade  foreman-postgresql-3.5.1-1.el8.noarch                    @foreman
    Upgraded foreman-postgresql-3.5.0-0.17.rc2.el8.noarch             @@System
    Upgrade  foreman-proxy-3.5.1-1.el8.noarch                         @foreman
    Upgraded foreman-proxy-3.5.0-0.1.rc2.el8.noarch                   @@System
    Upgrade  foreman-release-3.5.1-1.el8.noarch                       @foreman
    Upgraded foreman-release-3.5.0-0.1.rc2.el8.noarch                 @@System
    Upgrade  foreman-selinux-3.5.1-1.el8.noarch                       @foreman
    Upgraded foreman-selinux-3.5.0-0.1.rc2.el8.noarch                 @@System
    Upgrade  foreman-service-3.5.1-1.el8.noarch                       @foreman
    Upgraded foreman-service-3.5.0-0.17.rc2.el8.noarch                @@System
    Upgrade  foreman-vmware-3.5.1-1.el8.noarch                        @foreman
    Upgraded foreman-vmware-3.5.0-0.17.rc2.el8.noarch                 @@System
    Upgrade  rubygem-dynflow-1.6.8-1.el8.noarch                       @foreman
    Upgraded rubygem-dynflow-1.6.7-1.fm3_4.el8.noarch                 @@System
    Upgrade  ansible-collection-theforeman-foreman-3.8.0-1.el8.noarch @foreman-plugins
    Upgraded ansible-collection-theforeman-foreman-3.7.0-2.el8.noarch @@System
Scriptlet output:
   1 warning: /etc/foreman-installer/scenarios.d/katello-answers.yaml created as /etc/foreman-installer/scenarios.d/katello-answers.yaml.rpmnew
   2 ERROR: ld.so: object '/usr/libexec/coreutils/libstdbuf.so' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
   3 /sbin/restorecon: SELinux: Could not get canonical path for /etc/puppet/node.rb restorecon: No such file or directory.
   4 ERROR: ld.so: object '/usr/libexec/coreutils/libstdbuf.so' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
   5 /sbin/restorecon: SELinux: Could not get canonical path for /etc/puppet/node.rb restorecon: No such file or directory.
3

Problem resolved, this was due to the Operating System of the host changing from EL 8 to EL 8.7 and as such losing the designated installation media from the kickstart repositories.

1 Like
4

Hi,
i have the same error.
How do you have fixed it ?
Thank you

5

As mentioned in the solution, the operating system value had changed for the hosts (e.g. EL 8.7 rather than EL8). This caused a disconnect for the host to find the appropriate installation media, so the resolution was twofold:

  1. Disabling the automatic changing of host operating systems based on system facts (Settings > Facts).

  2. Editing the hosts to use the correct operating system value.

1 Like