[JIRA] (OVIRT-763) [Lago][rfe] ability to choose version to be installed

[Nadav Goldin (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22222#comment-22222 ] 

Nadav Goldin commented on OVIRT-763:
------------------------------------

In order to run it directly with {code} run_suite.sh {code} use:
{code}
./run_suite.sh -s http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/1427  basic-suite-master
{code}
This will prefer the RPMs found in the ovirt-engine_master_build, also, if you would like to use different resources(i.e. vdsm and engine), create a configuration file, assuming it is 'extra-sources':
{code}
$ cat extra-sources 
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/1427/
http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/1071/
{code}
and run: 
{code}
./run_suite.sh -s \"conf:/home/ngoldin/ovirt-system-tests/basic-suite-master/extra-sources\" basic-suite-master
{code}
the "-s" parameter can accept any parameter that repoman accepts, it is quite flexible, have a look at: http://repoman.readthedocs.io, [~pkliczew at redhat.com] - tell me how it works for you.

[~danken at redhat.com] - we have an open ticket for that https://ovirt-jira.atlassian.net/browse/OST-9 , though until it is completed - it should be fairly easy to run it locally by triggering the build_artifacts from the Jenkins job and passing the URL/or locally built RPMs to ./run_suite.sh.

> [Lago][rfe] ability to choose version to be installed
> -----------------------------------------------------
>
>                 Key: OVIRT-763
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-763
>             Project: oVirt - virtualization made easy
>          Issue Type: By-EMAIL
>            Reporter: Piotr Kliczewski
>            Assignee: infra
>
> I started to test using lago with master repos and my custom engine built.
> It was built on 7.10 one test failed and I noticed that newer engine was
> installed instead of my specific version. It seems that we need an ability
> to define which version of the rpms should be used during the tests.
> Thanks,
> Piotr



--
This message was sent by Atlassian JIRA
(v1000.482.6#100017)