We do update most of the important software on slaves via global_setup yet packages like the kernel and libraries are left behind. With Fedora this is not a big deal since we rebuild those every year yet there's still a bunch of CentOS systems which may need updating. Opening ticket to track the upgrade footprint and test updates if needed.
Any way we can automate this upgrade? are we using an Ansible playbook for
On Wed, Jun 20, 2018 at 1:02 PM Evgheni Dereveanchin (oVirt JIRA) <
EMEA VIRTUALIZATION R&D
As most of our slaves are VMs it's probably easiest to rebuild them instead of upgrading as that will conserve disk space thanks to thin template images. This is in place for Fedora 28 but not yet tested on CentOS 7. I can spawn a separate ticket from to implement this.
For now I've upgraded vm0002 on Staging and ~170 packages got updated including java and python libraries as well as other stuff. Put it online so that we can see if any incompatibilities are detected before upgrading the rest to move forward
I've also upgraded ovirt-srv24 bare metal that's attached to jenkins-staging - can we simulate an OST run to see if everything works fine? I can then upgrade bare metals and proceed to rebuilding VMs as part of the CVE patching process
The newly rebuilt bare metals ( ) were put online yesterday to help with the build queue and seem to be working fine so I'm unblocking work on this.
Also upgraded ovirt-srv22 and ovirt-srv25 which were unresponsive on the Jenkins and put those online as well. Before rebuilding VMs we'll need https://gerrit.ovirt.org/92418/ or https://gerrit.ovirt.org/93273/ to get merged to ensure global_setup can install all the software it needs. Here's a list of the upgraded 7.5 VMs live on the production jenkins: vm0004 vm0034 vm0035 vm0036