After upgrading to 1.13 (also, already to rc1/2), triggering a "rebuild config" via Foreman UI results in the following error message: 2016-10-06T15:15:09 41b4843f [app] [I] Started POST "/hosts/submit_rebuild_config?host_ids%5B%5D=9" for 2001:a62:14b:a301:xxx at 2016-10-06 15:15:09 +0200 2016-10-06T15:15:09 41b4843f [app] [I] Processing by HostsController#submit_rebuild_config as HTML 2016-10-06T15:15:09 41b4843f [app] [I] Parameters: {"utf8"=>"✓", "authenticity_token"=>"ZVbKXQGHxZwy9rHR8EGUiagzy99rjCE/8sL0KcVxqQUgb3iVhw1kEZxxx", "host_ids"=>["9"]} 2016-10-06T15:15:09 41b4843f [app] [I] Delete DHCP reservation for argon.example.com-00:25:90:0e:b4:c2/10.10.10.112 2016-10-06T15:15:09 41b4843f [app] [I] Create DHCP reservation for argon.example.com-00:25:90:0e:b4:c2/10.10.10.112 2016-10-06T15:15:09 41b4843f [app] [E] Failed to rebuild TFTP record for argon.example.com (10.10.10.112/2a02:xxxx) | ArgumentError: wrong number of arguments (0 for 1) | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:92:in `setTFTP' | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:39:in `rebuild_tftp' http://projects.theforeman.org/issues/16819
Upstream bug component is Provisioning Templates
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16819 has been resolved.
Is this upgrade specific, meaning should this be tested only after an upgrade from sat62 to sat63?
Just verify the rebuild button works, nothing to do with upgrades.
VERIFIED on sat6.3.0-17 - rebuilding works as a charm. - there's no longer a POST request to "/hosts/submit_rebuild_config" as this was refactored. - I was able to rebuild el7.4 x86_64 host to el6 i386 host. the TFTP pxelinux and grub config files got properly overwritten.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336