Bug 1334473
| Summary: | vdsm latest master requires python-yaml on el7, but it's not on any repos | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | David Caro <dcaroest> |
| Component: | Packaging.rpm | Assignee: | Piotr Kliczewski <pkliczew> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Aharon Canan <acanan> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.17.18 | CC: | bugs, danken, dcaroest, eedri, oourfali |
| Target Milestone: | ovirt-4.0.0-rc | Keywords: | AutomationBlocker, Regression |
| Target Release: | --- | Flags: | oourfali:
ovirt-4.0.0?
rule-engine: blocker? rule-engine: planning_ack? oourfali: devel_ack+ rule-engine: testing_ack? |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-10 11:03:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Caro
2016-05-09 17:31:15 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. 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. 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/ 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) (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 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 Yep, that solve the dependency issue much clearer now: David Caro 13:28 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 |