Plugins » Katello

Hi,

We are running foreman 1.16 and katello 3.5.0 and we are hitting the same issue as described here
http://projects.theforeman.org/issues/19976

all new machines already provisioning asking to reboot

Status Error
Configuration No changes
Errata All errata applied
Subscription Fully entitled
Traces Reboot required

We noticed that the problem is solved if you manually execute "katello-tracer-upload" or "yum install XXX" in the machine after the first boot.

Trying to workaround the issue we added this at the end of our provisioning template but it didn't solve the problem.

<% if @provisioning_type == nil || @provisioning_type == 'host' -%>
# Inform the build system that we are done.
echo "Informing Foreman that we are built" 
wget -q -O /dev/null --no-check-certificate <%= foreman_url('built') %>
<% end -%>
# if this host has the katello client installed we 
# execute katello-tracer-upload so it's not in error
# status after the first boot
<% if @host.params['kt_activation_keys'] %>
echo "executing katello-tracer-upload" 
/usr/sbin/katello-tracer-upload
<% end -%>
) 2>&1 | tee /root/install.post.log
exit 0

This is what we get in production.log when the machine is provisioned

2018-01-19 13:07:59 28bd6d73 [app] [I]   Parameters: {"traces"=>{"kernel"=>{"type"=>"static", "helper"=>"You will have to reboot your computer"}, "systemd"=>{"type"=>"static", "helper"=>"You will have to reboot your computer"}, "anaconda-shell@hvc0"=>{"type"=>"daemon", "helper"=>"systemctl restart anaconda-shell@hvc0"}, "chronyd"=>{"type"=>"daemon", "helper"=>"systemctl restart chronyd"}, "lvm2-lvmetad"=>{"type"=>"daemon", "helper"=>"systemctl restart lvm2-lvmetad"}, "systemd-udevd"=>{"type"=>"daemon", "helper"=>"systemctl restart systemd-udevd"}, "dbus"=>{"type"=>"static", "helper"=>"You will have to reboot your computer"}, "anaconda-shell@hvc1"=>{"type"=>"daemon", "helper"=>"systemctl restart anaconda-shell@hvc1"}, "polkit"=>{"type"=>"daemon", "helper"=>"systemctl restart polkit"}, "systemd-logind"=>{"type"=>"daemon", "helper"=>"systemctl restart systemd-logind"}, "systemd-journald"=>{"type"=>"daemon", "helper"=>"systemctl restart systemd-journald"}, "rsyslog"=>{"type"=>"daemon", "helper"=>"systemctl restart rsyslog"}, "anaconda"=>{"type"=>"session", "helper"=>"You will have to log out & log in again"}, "multipathd"=>{"type"=>"daemon", "helper"=>"systemctl restart multipathd"}, "NetworkManager"=>{"type"=>"daemon", "helper"=>"systemctl restart NetworkManager"}}, "id"=>"9fe4fb4c-6ee1-464e-9af8-abeca962f19a"}

These are the rpms installed in the privisioned machine

katello-host-tools-fact-plugin-3.1.0-1.el7.noarch
katello-host-tools-3.1.0-1.el7.noarch
katello-ca-consumer-katello-dmz.scicore-dmz.lan-1.0-1.noarch
katello-agent-3.1.0-1.el7.noarch

by now the only workaround is to manually execute "katello-tracer-upload" in the provisioned machine after the first boot