[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.pl... ] Evgheni Dereveanchin reassigned OVIRT-780: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra)

engine upgrade job is disabling puppet on slaves ------------------------------------------------

Key: OVIRT-780 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-780 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin Priority: Low Fix For: OVIRT-INFRA-NOV-2016

I found a lot of out-of-sync slaves in Foreman and further investigation revealed that puppet agent is disabled on them. The journal indicates that it's the upgrade job doing this: Oct 19 14:24:51 vm0079.workers-phx.ovirt.org sudo[18213]: jenkins : TTY=unknown ; PWD=/home/jenkins/workspace/ovirt-engine_master_upgrade-from-4.0_el7_created ; USER=root ; COMMAND=/bin/puppet agent --disable Oct 19 14:24:54 vm0079.workers-phx.ovirt.org puppet-agent[18215]: Disabling Puppet. The job seems to re-enable puppet after it runs, but once there's several consecutive jobs in the queue this causes puppet to be effectively turned off for hours. Do we really need this? Can we run engine upgrade jobs inside mock to not affect the node itself?

-- This message was sent by Atlassian JIRA (v1000.695.2#100025)