Bug 1374418

Summary: [RFE] Ability to filter VMs with next-run configuration
Product: [oVirt] ovirt-engine Reporter: Arik <ahadas>
Component: RFEsAssignee: Andrej Krejcir <akrejcir>
Status: CLOSED DUPLICATE QA Contact: Lukas Svaty <lsvaty>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.4CC: bkorren, bugs, rbarry, tjelinek
Target Milestone: ovirt-4.1.3Keywords: FutureFeature
Target Release: ---Flags: pm-rhel: ovirt-4.1?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-24 13:07:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Arik 2016-09-08 15:51:56 UTC
Now that we reuse the next-run configuration for indicating that there are running VMs that were started in the previous compatibility version of the cluster, it would be useful to provide the ability to filter these VMs in the UI.

Comment 1 Red Hat Bugzilla Rules Engine 2016-09-08 15:53:58 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 RHEL Program Management 2019-07-29 10:33:56 UTC
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 3 Andrej Krejcir 2019-09-17 12:40:46 UTC
*** Bug 1373803 has been marked as a duplicate of this bug. ***

Comment 4 Andrej Krejcir 2019-09-24 13:07:24 UTC

*** This bug has been marked as a duplicate of bug 1432912 ***