Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1470802

Summary: scheduling policy required properties have no defaults
Product: Red Hat Enterprise Virtualization Manager Reporter: Dusan Fodor <dfodor>
Component: ovirt-engineAssignee: Phillip Bailey <phbailey>
Status: CLOSED ERRATA QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.4CC: dfediuck, lsurette, mgoldboi, msivak, phbailey, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul
Target Milestone: ovirt-4.1.4Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-27 18:02:44 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:
Attachments:
Description Flags
scheduling_policy_tab none

Description Dusan Fodor 2017-07-13 17:29:08 UTC
Created attachment 1297774 [details]
scheduling_policy_tab

Description of problem:

When creating cluster, it is now required to define scheduling policy properties HighUtilization and CpuOverCommitDuration.
1. I'd expect some default values there.
2. The text field doesn't show any description (when hovering cursor on textfield) until it is highlighted red as incorrectly entered value. That may be different, UI bug though.
3. The description is in regexp format <^([5-9][0-9]*)$>, i'm not sure if it is the best human-readable form of description.

Version-Release number of selected component (if applicable):
rhv-4.1.4-3

How reproducible:


Steps to Reproduce:
1. try to add cluster in rhv-4.1.4
2. see Scheduling policy tab
3.

Comment 4 Artyom 2017-07-23 07:16:23 UTC
Verified on rhevm-4.1.4.2-0.1.el7.noarch

Comment 6 errata-xmlrpc 2017-07-27 18:02:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1814