Bug 1278491

Summary: Make the ovirt lago tests run for 3.6 stable engine
Product: [Community] ovirt-system-tests Reporter: David Caro <dcaroest>
Component: CoreAssignee: David Caro <dcaroest>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, eedri, tlitovsk
Target Milestone: milestone2   
Target Release: 0.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ci
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1282691 (view as bug list) Environment:
Last Closed: 2016-01-26 09:16:13 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: 1277649    
Bug Blocks: 1278500, 1279411    

Description David Caro 2015-11-05 15:31:44 UTC
Description of problem:
Right now we are only runnig on 3.5 stable, as a step towards get it running for all versions, 3.6 stable should be next

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2015-11-05 15:31:47 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Red Hat Bugzilla Rules Engine 2015-11-05 15:31:47 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 3 Eyal Edri 2015-11-05 15:42:51 UTC
for this to work we need to create a stable repo to hold latest stable (currently 0.3) and also latest repo.

also related to: Bug 1277650 - Automate the lago rpm distribution
https://bugzilla.redhat.com/show_bug.cgi?id=1277650

tolik,
would you be able to take ownership on this once the blocker bug will be done?

Comment 4 Red Hat Bugzilla Rules Engine 2015-11-05 15:42:54 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Red Hat Bugzilla Rules Engine 2015-11-05 15:42:54 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 6 Eyal Edri 2015-11-05 15:48:04 UTC
for this to work we need to create a stable repo to hold latest stable (currently 0.3) and also latest repo.

also related to: Bug 1277650 - Automate the lago rpm distribution
https://bugzilla.redhat.com/show_bug.cgi?id=1277650

This bug means to add 3.6 jenkins job, another bug will be opened to verify the readme is updated for 3.6

Comment 7 Red Hat Bugzilla Rules Engine 2015-11-05 15:48:07 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 8 Red Hat Bugzilla Rules Engine 2015-11-05 15:48:07 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 9 Red Hat Bugzilla Rules Engine 2015-11-05 15:49:30 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 10 Red Hat Bugzilla Rules Engine 2015-11-12 10:19:05 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 11 Eyal Edri 2015-11-19 08:06:04 UTC
link to 3.6 tests: http://jenkins.ovirt.org/view/System%20tests/job/ovirt_3.6_system-tests/

Comment 12 David Caro 2016-01-26 09:16:13 UTC
Tests are running ok and already finding issues