[JIRA] (OVIRT-639) Fix Puppet config loop on FC23 hosts

Fix Puppet config loop on FC23 hosts ------------------------------------ Key: OVIRT-639 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-639 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: Evgheni Dereveanchin It seems we have a Puppet configuration loop on FC23, when running Puppet it always yields this log: {quote} /usr/share/ruby/vendor_ruby/puppet/defaults.rb:488: warning: duplicated key at line 489 ignored: :queue_type Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for ovirt-srv09.phx.ovirt.org Info: Redefining firewalld_rich_rule in Puppet::Type Info: Applying configuration version 'production:Sun Jul 17 14:20:57 CEST 2016' Notice: /Stage\[main]/Ovirt_jenkins_slave::Base/Package\[java-1.8.0-openjdk-devel]/ensure: ensure changed '1.8.0.91-6.b14.fc23' to '1:1.8.0.92-4.b14.fc23' Notice: /Stage\[main]/Ovirt_jenkins_slave::Base/Package\[java-1.8.0-openjdk]/ensure: ensure changed '1.8.0.91-6.b14.fc23' to '1:1.8.0.92-4.b14.fc23' Notice: /Stage\[main]/Ovirt_jenkins_slave::Base/Package\[qemu-kvm]/ensure: ensure changed '2.4.1-9.fc23' to '2:2.4.1-11.fc23' Notice: /Stage\[main]/Ovirt_jenkins_slave::Mock_builder/Package\[mock]/ensure: ensure changed '1.2.17-1.fc23' to '0:1.2.18-1.fc23' Notice: /Stage\[main]/Ovirt_jenkins_slave::Base/Package\[java-1.8.0-openjdk-headless]/ensure: ensure changed '1.8.0.91-6.b14.fc23' to '1:1.8.0.92-4.b14.fc23' Notice: /Stage\[main]/Ovirt_infra::Packages/Package\[vim-minimal]/ensure: ensure changed '7.4.1718-1.fc23' to '2:7.4.1868-1.fc23' Notice: /Stage\[main]/Ovirt_jenkins_slave::Base/Package\[libvirt]/ensure: ensure changed '1.2.18.3-1.fc23' to '0:1.2.18.3-2.fc23' Notice: /Stage\[main]/Puppet::Agent::Service/Service\[puppet]/ensure: ensure changed 'stopped' to 'running' Info: /Stage\[main]/Puppet::Agent::Service/Service\[puppet]: Unscheduling refresh on Service\[puppet] Notice: Finished catalog run in 34.34 seconds {quote} We need to fix this because this will flood foreman with false-positive change reports.