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:
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.
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.
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?
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
link to 3.6 tests: http://jenkins.ovirt.org/view/System%20tests/job/ovirt_3.6_system-tests/
Tests are running ok and already finding issues