Bug 1316456
Summary: | Cannot change scheduling policy cluster overrides over REST API - changes affect the global scheduling policy instead | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Roman Mohr <rmohr> |
Component: | RestAPI | Assignee: | Nobody <nobody> |
Status: | CLOSED WONTFIX | QA Contact: | Petr Matyáš <pmatyas> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0.0 | CC: | alukiano, bugs, dfediuck, lsvaty, mgoldboi, rbarry, rgolan |
Target Milestone: | --- | Keywords: | AutomationBlocker, Regression |
Target Release: | --- | Flags: | dfediuck:
ovirt-4.3?
rule-engine: blocker? rule-engine: planning_ack? rule-engine: devel_ack? lsvaty: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-24 00:23:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Roman Mohr
2016-03-10 09:59:27 UTC
On 4.0 the embedded scheduling policy is now external which makes it currently impossible to set cluster scheduling properties through the REST API. Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA. oVirt 4.0 beta has been released, moving to RC milestone. oVirt 4.0 beta has been released, moving to RC milestone. Moving to 4.1, as this is the current implementation and not a regression. 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. I believe we need to up the severity, because it prevents from automation to check all built-in scheduling policies This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. (In reply to Doron Fediuck from comment #5) > Moving to 4.1, as this is the current implementation and not a regression. It is a regression. It is one thing that the REST-API was always misleading. But in 4.0 it is now impossible to update the properties of a policy for a cluster. You always change the "template" policy which means that you set the property for all clusters which are using this policy. This was introduced by the REST-API refactoring for 4.0. Closing, since there are no reports from the field in years, and there is a lack of capacity to work on this |