Hi, I need to test patch for upgrade from newest 4.1.7. Upgrade_from_release gives me ovirt-engine-4.1.6.2. Is there some way how to choose particular version?

Regars, Mirka V.

On Mon, Oct 16, 2017 at 6:18 PM, Miroslava Voglova <mvoglova(a)redhat.com&gt; wrote: > Hi, > > I need to test patch for upgrade from newest 4.1.7. Upgrade_from_release > gives me ovirt-engine-4.1.6.2. > Is there some way how to choose particular version? > If you need to test upgrade from newer engine, you can specify the link to the newer engine RPMs from build-artifacts job. It works well for basic suite, though not sure we tested how it affects upgrade suite. If it doesn't work, you can always run it locally and tweak the relevant repos. What are you trying to test? upgrade from 4.1.7 latest to master?

> > Regars, > Mirka V. > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 <+972%209-769-2018> irc: eedri (on #tlv #rhev-dev #rhev-integ)

On Mon, Oct 16, 2017 at 6:48 PM, Martin Perina <mperina(a)redhat.com&gt; wrote: > > > On Mon, Oct 16, 2017 at 5:42 PM, Eyal Edri <eedri(a)redhat.com&gt; wrote: > >> >> >> On Mon, Oct 16, 2017 at 6:18 PM, Miroslava Voglova <mvoglova(a)redhat.com&gt; >> wrote: >> >>> Hi, >>> >>> I need to test patch for upgrade from newest 4.1.7. >>> Upgrade_from_release gives me ovirt-engine-4.1.6.2. >>> Is there some way how to choose particular version? >>> >> >> If you need to test upgrade from newer engine, you can specify the link >> to the newer engine RPMs from build-artifacts job. >> It works well for basic suite, though not sure we tested how it affects >> upgrade suite. >> >> If it doesn't work, you can always run it locally and tweak the relevant >> repos. >> >> What are you trying to test? upgrade from 4.1.7 latest to master? >> > > ​Right we need to test upgrade from latest 4.1.z (latest tested) to the > master with our patch. But unless I miss something, we can ​specify repo > only for target version of the upgrade, but not the source one. It seems > that upgrade OST always takes latest released as source for upgrade. Or am > I missing something? > > I rerun you job [1], now using latest tested, if that doesn't work, we'll probably need to run it locally with some update to the reposync file [1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ ovirt-system-tests_manual/1378/console