Description of problem: If an rpm scriptlet fails, yum considers this non-fatal, and emits a suitable error. However, otopi does consider it fatal and fails the transaction. See also bug 1493160 and bug 1493033. To help debug such failures, it would be useful to have otopi run with rpmverbosity = "debug", which (among other things) causes rpm to run the scriptlets with 'set -x'/'set -o xtrace' and log stdout/stderr to its logs, which inside otopi goes to otopi's log, which is the relevant tool's log (host-deploy, engine-setup etc). This was already done in oVirt 4.2/otopi-1.7 [1], opening current bug for 4.1. Patch cherry-picked and verified [2]. [1] https://gerrit.ovirt.org/81993 [2] https://gerrit.ovirt.org/82128
in host-deploy or mgmt logs yum prints more informations e.g. 2018-01-17 13:17:51 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Status: Running Transaction 2018-01-17 13:17:52 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum install: 1/262: satyr-0.13-14.el7.x86_64 XZDIO: 68 reads, 2319412 total bytes in 0.059597 secs 2018-01-17 13:17:52 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Script sink: D: closed db index /var/lib/rpm/Obsoletename D: closed db index /var/lib/rpm/Conflictname D: closed db index /var/lib/rpm/Providename ... verified in otopi-1.6.3-1.el7ev.noarch with ovirt-engine-4.1.9-0.2.el7.noarch
This bugzilla is included in oVirt 4.1.9 release, published on Jan 24th 2018. Since the problem described in this bug report should be resolved in oVirt 4.1.9 release, published on Jan 24th 2018, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.