Bug 1334473 - vdsm latest master requires python-yaml on el7, but it's not on any repos
Summary: vdsm latest master requires python-yaml on el7, but it's not on any repos
Alias: None
Product: vdsm
Classification: oVirt
Component: Packaging.rpm
Version: 4.17.18
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-rc
: ---
Assignee: Piotr Kliczewski
QA Contact: Aharon Canan
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-09 17:31 UTC by David Caro
Modified: 2016-06-26 23:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-05-10 11:03:08 UTC
oVirt Team: Infra
oourfali: ovirt-4.0.0?
rule-engine: blocker?
rule-engine: planning_ack?
oourfali: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 57286 0 master NEW spec: change python-yaml to PyYAML 2016-05-10 06:57:43 UTC

Description David Caro 2016-05-09 17:31:15 UTC
Description of problem:
YumBaseError: [u'vdsm-4.17.999-1071.gite57b69e.el7.centos.x86_64 requires python-yaml']

Instead I can find PyYAML, maybe that one should be required in the spec instead?

The repos I have enabled are centos-base, updates, extras, epel and ovirt-master-snapshot + snapshot-static

Version-Release number of selected component (if applicable):
I'm using latest vdsm from master-snapshot repo

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Yaniv Kaul 2016-05-09 19:01:55 UTC
Looks like it's working indeed with PyYAML:
[ykaul@ykaul ~]$ sudo dnf install python-yaml
[sudo] password for ykaul: 
Last metadata expiration check: 5:47:48 ago on Mon May  9 16:13:37 2016.
Package PyYAML-3.11-11.fc23.x86_64 is already installed, skipping.

Comment 2 Red Hat Bugzilla Rules Engine 2016-05-10 05:47:12 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Dan Kenigsberg 2016-05-10 06:48:09 UTC
It's easy to s/python-yaml/PyYAML/ but I don't understand where did you see the failure. We should understand why note of our CI tests has caught this https://gerrit.ovirt.org/#/c/52864/

Comment 4 David Caro 2016-05-10 07:55:59 UTC
I see the failure in the http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_master_system-tests/.

It was not cached by the vdsm tests because all the tests it does are on fc23 (so there's never an installation test one el7)

Comment 5 Oved Ourfali 2016-05-10 08:02:36 UTC
(In reply to David Caro from comment #4)
> I see the failure in the
> http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_master_system-
> tests/.
> It was not cached by the vdsm tests because all the tests it does are on
> fc23 (so there's never an installation test one el7)

Can you point to a specific run? I want to make sure we're looking at the same right log.

Also, can you check if applying [1] solves this?

[1] http://gerrit.ovirt.org/57286

Comment 6 David Caro 2016-05-10 08:08:24 UTC
The last two for example, though there's a bug and the logs where not collected (on it, that's one of the things I was debugging when I saw that error).
I ran it manually on the host and saw the logs properly there (the string pasted in the desc is part of the host-deploy logs).

You can try it yourself locally with any el7 machine/vm/chroot/container, just add the ovirt-master-snapshot repo and run yum install vdsm.

I'll try to apply the patch

Comment 7 David Caro 2016-05-10 08:36:42 UTC
Yep, that solve the dependency issue

Comment 8 Dan Kenigsberg 2016-05-10 11:03:08 UTC
much clearer now:

David Caro

Patch Set 4:

Actually, I just found out that the issue is not with vdsm itself, if you run vdsm with the repos, it will install PyYAML when python-yaml is a dependency, the problem is with the reposync we do for the tests, that when specifying python-yaml does not bring PyYAML in, and thus, PyYAML is not available for the hosts in the tests (yum install python-yaml does not work as a result).

So though this patch does not break anything and might be less confusing as the deps in the spec have the same name as the packages, it turns out it was not needed, sorry about that

Note You need to log in before you can comment on or make changes to this bug.