Bug 1432912
Summary: | [RFE] add search query for "next run configuration exists" | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Jiri Belka <jbelka> |
Component: | Frontend.WebAdmin | Assignee: | Shmuel Melamud <smelamud> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | future | CC: | ahadas, bugs, danken, lsvaty, michal.skrivanek, mkalinin, mtessun, stirabos, tjelinek |
Target Milestone: | ovirt-4.1.3 | Keywords: | FutureFeature |
Target Release: | 4.1.3.2 | Flags: | rule-engine:
ovirt-4.1+
mtessun: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
It is now possible to search for VMs that have pending configuration changes. The search query is "Vms: next_run_configuration_exists=True"
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-06 13:13:34 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1489245 |
Description
Jiri Belka
2017-03-16 12:06:46 UTC
Raising severity, as keeping such VMs running is not recommended. Users need to easily tell how much of them exist, so they can plan power cycles for them all. it's not a regular entity field so it cannot be done easily. Would probably require a specific hack to handle this particular case Also, see bug 1436577 and we also miss search on cluster compatibility level actually, the search on cluster override would be enough Michal - can we set it for 4.1.3? Renamed this RFE back, because another RFE will be created for searching by cluster compatibility level override. Bug 1454389 created. ok, ovirt-engine-4.1.3.2-0.1.el7.noarch *** Bug 1374418 has been marked as a duplicate of this bug. *** |