Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1651552

Summary:	[downstream clone - 4.2.8] vdsm-client has missing dependecy to PyYAML
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	RHV bug bot <rhv-bugzilla-bot>
Component:	vdsm	Assignee:	Marcin Sobczyk <msobczyk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2.6	CC:	lleistne, lsurette, mgoldboi, mperina, srevivo, ycui
Target Milestone:	ovirt-4.2.8	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	v4.20.45	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1645620	Environment:
Last Closed:	2019-01-31 08:30:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1645620
Bug Blocks:

Description RHV bug bot 2018-11-20 10:28:45 UTC

+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1645620 +++
======================================================================

Description of problem:
During the installation of a fresh installed host the vdsm-client package throws a traceback in %post.

Version-Release number of selected component (if applicable):
vdsm-client-4.20.39.1-1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install host
2. Install host via RHV-management ui

Actual results:
Installation is failing, traceback shown in ovirt-host-deploy log

D: %post(vdsm-client-4.20.39.1-1.el7ev.noarch): execv(/bin/sh) pid 23213
+ /usr/bin/python -c 'from vdsm.api.vdsmapi import create_cache; create_cache()'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/vdsm/api/vdsmapi.py", line 27, in <module>
    import yaml
ImportError: No module named yaml
D: %post(vdsm-client-4.20.39.1-1.el7ev.noarch): waitpid(23213) rc 23213 status 100
warning: %post(vdsm-client-4.20.39.1-1.el7ev.noarch) scriptlet failed, exit status 1

2018-11-02 10:33:58,045+0100 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Done: vdsm-client.noarch 0:4.20.39.1-1.el7ev - u
2018-11-02 10:33:58,047+0100 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum Non-fatal POSTIN scriptlet failure in rpm package vdsm-client-4.20.39.1-1.el7ev.noarch


Expected results:
No traceback, PyYAML included in vdsm-client's dependency list.

Additional info:

# rpm -q --requires vdsm-client
/bin/sh
/usr/bin/python2
python
python(abi) = 2.7
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
vdsm-api = 4.20.39.1-1.el7ev
vdsm-api = 4.20.39.1-1.el7ev
vdsm-python = 4.20.39.1-1.el7ev
vdsm-yajsonrpc = 4.20.39.1-1.el7ev
rpmlib(PayloadIsXz) <= 5.2-1

(Originally by Andreas Bleischwitz)

Comment 2 RHV bug bot 2018-11-20 10:28:54 UTC

We have a dependency on PyYAML in vdsm, but we forgot to add it to vdsm-client.

The strange thing is that on all our testing systems yum installed vdsm package before vdsm-client, so this issue haven't been observed.

The workaround is to install PyYAML on the host manually before you try to add host in RHV Manager.

(Originally by Martin Perina)

Comment 3 Pavel Novotny 2019-01-10 19:36:58 UTC

Verified in 
ovirt-engine-4.2.8.2-0.1.el7ev.noarch
vdsm-4.20.46-1.el7ev.x86_64

Installation of the host from the webadmin web UI completed successfully.
PyYAML is installed on the system in the host deploy phase:

-~-
# grep PyYAML /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20190110200926-host42-1-25b5ce3e.log
...
2019-01-10 20:03:48,090+0100 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum     install    - PyYAML-3.10-11.el7.x86_64
2019-01-10 20:03:48,217+0100 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.processTransaction:268     install - PyYAML-3.10-11.el7.x86_64
...
...
2019-01-10 20:03:48,583+0100 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Downloading: (3/446): PyYAML-3.10-11.el7.x86_64.rpm (0%)
2019-01-10 20:03:48,587+0100 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Download/Verify: PyYAML-3.10-11.el7.x86_64
2019-01-10 20:03:48,590+0100 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Downloading: (3/446): PyYAML-3.10-11.el7.x86_64.rpm 153 k(100%)
2019-01-10 20:05:39,707+0100 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum install: 120/447: PyYAML-3.10-11.el7.x86_64
...
2019-01-10 20:05:39,837+0100 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Done: PyYAML-3.10-11.el7.x86_64
2019-01-10 20:08:42,700+0100 INFO otopi.plugins.otopi.packagers.yumpackager yumpackager.info:80 Yum Verify: 241/447: PyYAML.x86_64 0:3.10-11.el7 - u
# rpm -q PyYAML
PyYAML-3.10-11.el7.x86_64
-~-

Comment 4 Martin Perina 2019-01-31 08:30:09 UTC

This was shipped as a part of https://errata.devel.redhat.com/advisory/38170