Description of problem: engine-setup and related tools should support dnf [1]. [1] http://dnf.baseurl.org/
Setting version to 3.6 for now, not sure what's the timeline of dnf in fedora etc.
Not blocking F22 support since yum python module are still available in F22.
OTOPI 1.4.0 introduced DNF support, if we don't add support for it to ovirt-engine, upgrade will be broken.
Fixing target milestone to ovirt-4.0.0 for the time being. We are not going to make it to ovirt-3.6.0-3.6.3 for sure.
This bug is marked for z-stream, yet the milestone is for a major version, therefore the milestone has been reset. Please set the correct milestone or drop the z stream flag.
(In reply to Yaniv Kaul from comment #4) > Fixing target milestone to ovirt-4.0.0 for the time being. We are not going > to make it to ovirt-3.6.0-3.6.3 for sure. Why not? It was a 4.0 planned feature but suddenly dnf support has been added to otopi 1.4, breaking upgrade on Fedora 22. We need to support DNF to some extent in 3.6 as well or drop dnf support in otopi 1.4.
Proposing 3.6.1 milestone since a patch is already under review on master.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
(In reply to Sandro Bonazzola from comment #8) > Proposing 3.6.1 milestone since a patch is already under review on master. if it's not ready now, better to move to 3.6.2, right?
right
Reducing severity to medium, don't see why it had high severity in the first place.
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA
Closing older BZs, if still happened, please reopen.