Red Hat Bugzilla – Bug 1472812
Running engine-host-update.py does not work with RHVH / RHEVH hosts
Last modified: 2017-09-15 02:57:39 EDT
Description of problem:
Running engine-host-update.py for RHVH hosts
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run `./engine-host-update.py --insecure --engine=localhost --username=admin@internal --password=mypass` --host=rhevh
RHVH host is reinstalled. Updates still available.
When host is upgraded properly.
Which version is the RHVH host are you trying to update?
It was upgrade 4.1.3 -> 4.1.4 candidate.
However problem is not in host, rather in the utility, current flow:
1. Deactivate host
2. Reinstall host
3. Activate host
Reinstall host uses this code:
My wild guess:
This method reinstalls the current image
a) for rhel hosts installs the packages and redeploy vdsm/libvirt..., which is correct
b)for rhevh it I believe it just reinstalls the current image, even that new image is available. For new image to be installed, upgrade should be used, not install/reinstall.
Do we want to fix this?
When is the Ansible to do this planned to be released?
(In reply to Yaniv Lavi (Dary) from comment #3)
> Do we want to fix this?
I do. Most of our install base is using RHVH.
> When is the Ansible to do this planned to be released?
4.1.6, according to Bug 1473535
Making this work with the vintage node is more critical, than RHVH.
(In reply to Yaniv Lavi (Dary) from comment #5)
> Making this work with the vintage node is more critical, than RHVH.
I talked to mperina@ and he clarified how 'install' works.
1. first 'host.install' action does check what is host type:
- if EL host, it _only_ installs packages which should are defined in
- if node (and legacy?) it supposes it has all packages available
2. even "installing" packages on EL host does _NOT_ update all packages. These
are defined in the DB (PackageNamesForCheckUpdate), thus simple 'host.install'
won't update all packages in (PackageNamesForCheckUpdate).
3. for node/ngn I suppose 'host.install' does not touch any packaging and
upgrade-manager updates 'ovirt-node-ng-image-update'
('OvirtNodePackageNamesForCheckUpdate' in DB) to update node/ngn.
Thus to update node/ngn (and to correct vds_type if it has been wrong) it would need to to reinstall ('host.install') and tell upgrade-manager to upgrade it as well.