Seems the problem, atleast part of it (because still, it doesn't get to the 
part of creating the imgbase layer) is related to the /tmp/yum_updates file.
/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-check-upgrade/tasks/main.yml
yum check-update -q | cut -d ' ' -f1 | sed '/^$/d' >> /tmp/yum_updates
For some reason it also lists those packages:
gluster-ansible-cluster.src
gluster-ansible-infra.src
gluster-ansible-maintenance.src
gluster-ansible-roles.src

Which do not exists, those are source RPMs, so the ansible playbook for the 
host upgrade fails.

I did a quick workaround and added an "egrep -v src"
yum check-update -q | egrep -v src | cut -d ' ' -f1 | sed '/^$/d' >> 
/tmp/yum_updates

So now the ansible-playbook doesn't fail, it does says the upgrade was 
successful the host reboots, but it doesn't get upgraded.

Also, i noticed that the playbook does make sure that the dnf cache is up to 
date (update_cache is set to true) when first checking the ovirt-host package, 
but it also does this for every single package in the task after, so there's no 
need for update_cache there.

As a workaround to upgrade to 4.4.2 i have to reinstall every host with oVirt 
node 4.4.2 as it seems the upgrade process is broken.
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/GMZ5WLCYMFDSFBNTXFNOZU6ANYESSQ4H/

Reply via email to