Verifying an oVirt patch with ovirt-system-tests

On your laptop

Please follow the guidelines to run & install Lago & OST before trying this step.

Once you have everything set and you managed to run locally a basic ost suite without issues,
The only change you need to do is add ‘-s’ to your command line, and provide a URL with the custom
RPMs you built for your patches ( see build-on-demand on how to build RPMs from an open patch. )

Example of running a suite locally with a custom repo: (from the OST root dir)

./run_suite.sh -s http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x86_64/1/ basic_suite_master

On Jenkins

On some occassions running OST on your laptop might not be possible due to various reasons (time/resources/etc..)
So another easy option is to run a manual OST job on CI on your desired open patch(es).

To run an OST job on any open oVirt patch follow the following guidelines:

  • Build RPMs from your open patch(es)

    Building RPMs today from any open oVirt patch is simple as just asking for it.. :)
    The new ‘build-on-demand’ option from oVirt Standard CI allows you to just type ci please build in a comment on your patch and a new build will be triggered on the project ‘build-on-demand’ jobs.
    Once the ‘build-on-demand’ job finished building, write down the job URL, for e.g: vdsm-master-build-on-demand. (btw, you can do this for as many oVirt projects you want and have a list of URLs).

  • Run the manual OST job with your custom RPMs

    Now that you have your custom RPMs ready, you’re a click away from running OST on them.

    • Login to Jenkins (make sure you have ‘dev role’ permissions, if not open a ticket to infra)
    • Go to the OST Manual job for your relevant version ( usually master ).
    • Click on ‘build with parameters’ menu ( on the left side )
    • Now add all the URLs you have with the custom RPMs ( one per line ),for e.g vdsm-build
    • Choose a fallback_repo:
      A base repo that will be used ‘under’ your tested patch.
      latest: includes all the rpm’s that passed CI.
      latest_release: includes all the rpm’s in the latest release.
    • Choose the suite type you want:
      basic: Run engine-setup, and basic tests (bootstrap, sanity and etc)
      upgrade: Initialize the engine with a base version, test if an upgrade to the target
      version is possible.
      Here we have 3 options:
      upgrade-from-rc: The base version installed (before the upgrade) is the current release candidate
      upgrade-from-release: Depends on the target version, the current official release will be set as the
      base installed version from which we will upgrade.
      e.g, if you choose upgrade from release for oVirt-4.1, the suite will install the official release of 4.1
      and upgrade to the latest repo with your patch on top of it.
      upgrade-from-prevrelease: Depends on the target version, the previous official release will be set as the
      base installed version from which we will upgrade.
      e.g, if you choose upgrade from release for oVirt-4.1, the suite will install the official release of 4.0
      and upgrade to the latest repo with your patch on top of it.
    • Choose the engine_version: This is the version that we actually test.
      (in the upgrade suites, this is the version that we will be upgrading to)
    • Choose the lago_version (unless you are testing lago, you’ll probably want the stalbe release)
    • Click ‘Build’
    • Go have coffee, don’t worry the job will send you an email once its done ( on any status )

If you’re having issues or have any questions, please contact the infra team at infra@ovirt.org.