ovirt-system-tests_manual against specific version

[Daniel Belenky]

On Mon, Oct 16, 2017 at 6:51 PM, Eyal Edri <eedri at redhat.com> wrote:

>
>
> On Mon, Oct 16, 2017 at 6:48 PM, Martin Perina <mperina at redhat.com> wrote:
>
>>
>>
>> On Mon, Oct 16, 2017 at 5:42 PM, Eyal Edri <eedri at redhat.com> wrote:
>>
>>>
>>>
>>> On Mon, Oct 16, 2017 at 6:18 PM, Miroslava Voglova <mvoglova at redhat.com>
>>> 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
>

I see that in the test you've attached in your mail used
ovirt-engine-setup-4.2.0 which was built in
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-on-demand-el7-x86_64/520
.
Please note that using "*latest-tested*" as a fallback repo is risky (your
test might fail because this repo is being changed constantly) and is* not
recommended* at all. It has nothing to do with the RPMs that you want to
fetch from the CUSTOM_REPOS you've added.
Please feel free to ping me via IRC (dbelenky) #rhev-integ or #rhev-dev
with questions regarding the manual suite, I'll be happy to help :)
-- 

DANIEL BELENKY

RHV DEVOPS

EMEA VIRTUALIZATION R&D
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20171017/ac628548/attachment-0001.html>