[
https://ovirt-jira.atlassian.net/browse/OVIRT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22212#comment-22212
]
Evgheni Dereveanchin commented on OVIRT-780:
--------------------------------------------
Logged ovirt-808 to track moving upgrade jobs to lago - that should fix the
issue. In general, disabling puppet during a job run is not critical and is
only visible when there's a lot of builds so dozens of nodes get stale on
Foreman. I think we can close this case.
> 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.482.6#100017)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
