Please fix ovirt-system-test for 4.1-pre
Description
Activity
Eyal Edri February 4, 2017 at 3:39 PM
I wasn't aware 4.1-pre isn't a full composed repo and requires also ovirt-4.1 repo to work.
We'll need to update the reposync file on OST 4.1 to include the ovirt-4.1 repo as well in that case.
Sandro Bonazzola February 3, 2017 at 12:26 PM
This is relevant for all upcoming releases in 4.1.z timeframe.
ovirt-4.1-pre will be populated only with new packages to be tested on top of ovirt-4.1 repo.
Former user February 3, 2017 at 11:27 AM
The problem is ovirt-4.1-pre doesn't contain all rpms after release as it's layered repo so reposync config must include http://resources.ovirt.org/pub/ovirt-4.1/ repo otherwise dependencies will not be satisfied. This is relevant to asyncs only.
Am I right?
Sandro Bonazzola February 3, 2017 at 10:31 AM
ovirt-4.1-pre is a layered repository on top of ovirt-4.1.
ovirt-4.1-pre won't never pass repository closure alone.
Former user February 3, 2017 at 10:30 AM
Not sure if it's related but the failures was started right after <latestOnly>false</latestOnly>
removal and all missed packages have missed ovirt-4.1-pre mapping in the yamls
Former user February 3, 2017 at 10:28 AM
http://jenkins.ovirt.org/job/ovirt_4.1_system-tests_pre/23/
plenty of packages are missed in http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/el7/noarch/
Barak Korren February 3, 2017 at 9:48 AM
please link both failed runs.
Tried to use it for testing 4.1-pre repo with 4.1 async release and fails
on missing packages.
Tried also the manual job specifying both 4.1-pre and 4.1 repos, hoping
this would have fixed the missing packages requirements but it fails again.
Not enough time today for investigating myself.
–
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com