Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1279411

Summary:	[RFE] provide a way to run oVirt sanity testing through jenkins
Product:	[Community] ovirt-system-tests	Reporter:	Oved Ourfali <oourfali>
Component:	RFEs	Assignee:	Eyal Edri <eedri>
Status:	CLOSED DEFERRED	QA Contact:	Eyal Edri <eedri>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	0.3	CC:	bugs, eedri, mperina
Target Milestone:	---	Keywords:	Automation, FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ci
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-16 09:02:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1277492, 1277649, 1278491, 1282691
Bug Blocks:

Description Oved Ourfali 2015-11-09 12:19:27 UTC

We would like to run the basic sanity testing for oVirt using lago on jenkins.
We will supply link for engine/vdsm/any-other-package-built by lago, and we want the test to run on that patch.

We would need that for master, and 3.6.

Comment 1 Red Hat Bugzilla Rules Engine 2015-11-11 08:22:09 UTC

This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.

Comment 2 David Caro 2015-11-11 10:36:13 UTC

This has two sections, and not all of them are really related to lago (but hopefully we can add a plugin to do it)

* building rpms from a patch (now that we have standard ci, it should be easy to be able to pass any stardard-ci project)
* Using those rpms to create the repo that is passed to the vms BZ#1279962)
* Running the basic_suite (BZ#1278491 + another for master branch)

Comment 3 David Caro 2015-11-11 11:15:26 UTC

hehehe, that's how I count :)

Comment 4 Mike McCune 2016-03-28 22:26:18 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Eyal Edri 2016-04-10 13:49:49 UTC

Changing assignee, please feel free to re-assign to relevant teams.

Comment 6 Eyal Edri 2016-04-10 15:20:18 UTC

In progress:

3.6 is pending a fix for network issue for ovirt:
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_3.6_system-tests/

Currently runs nightly.

4.0 is still in progress (see attached patch for ovirt-system-tests):
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_master_system-tests/

Comment 7 Eyal Edri 2016-06-19 12:36:23 UTC

3.6, 4.0 and master are working.
Waiting for a decision if to enable API V4.

Comment 8 Eyal Edri 2016-06-26 07:52:24 UTC

It might be possible now to use the new experimental flow that deploys any new built package into the experimental repo and run verification on it via OST.

However, today it runs on merged commits to ALL projects, we'll need to think how to enable it per patch, but manually, via jenkins job or HOOK in gerrit.

Comment 9 Michal Skrivanek 2022-09-16 09:02:07 UTC

OST is not using bugzilla for tracking for a while, closing outstanding open bugs.
If you wish to follow up on this issue please do so at https://github.com/oVirt/ovirt-system-tests