[ https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22000#comment-22000 ] Barak Korren commented on OVIRT-780: ------------------------------------ We need this because engine-setup does not know how to recover from a locked yum. Effectively this means that if Puppet runs while engine-setup is running, the engine-setup will fail. Engine upgrade cannot run inside mock because it needs access to things like systemd which are not typically found inside mock. We've discussed this in the past, we should have a ticket somewhere to migrate the upgrade jobs to Lago.

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: infra Priority: Low

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.456.2#100016)