Details

    • Type: Improvement
    • Status: Done
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: OVIRT-INFRA-NOV-2016
    • Component/s: None
    • Labels:
      None

      Description

      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?

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                ederevea Evgheni Dereveanchin
                Reporter:
                ederevea Evgheni Dereveanchin
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: