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

Bug 1467056

Summary: Cluster creation via REST results in empty scheduling policy properties fields in the UI
Product: [oVirt] ovirt-engine Reporter: Nelly Credi <ncredi>
Component: Frontend.WebAdminAssignee: Phillip Bailey <phbailey>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: alukiano, bugs, dfediuck, mavital, ncredi, obensass
Target Milestone: ovirt-4.2.0Keywords: Triaged
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: planning_ack+
dfediuck: devel_ack+
mavital: 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: 2017-12-20 10:56:02 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
screenshot of the empty fields none

Description Nelly Credi 2017-07-02 10:22:14 UTC
Created attachment 1293599 [details]
screenshot of the empty fields

Description of problem:
When creating a cluster via REST API, the operation succeeds, but afterwards, when looking in the UI we can see that the scheduling policy properties - highUtilization & cpuOvercommitDurationMinutes are empty. In the rest they appear as expected.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170627181935.git9424f9b.el7.centos.noarch
ovirt-engine-restapi-4.2.0-0.0.master.20170627181935.git9424f9b.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. create cluster via REST API 
2. open the webadmin and check the cluster scheduling policy properties 
3.

Actual results:
In the UI the scheduling policy properties dont appear 

Expected results:
scheduling policy properties should appear in the UI

Additional info:

in REST we can see that the values exist:

<cluster href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c" id="65316857-7513-45a1-8183-57706fb8639c">
<actions>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/resetemulatedmachine" rel="resetemulatedmachine"/>
</actions>
<name>golden_env_mixed_1</name>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/glusterhooks" rel="glusterhooks"/>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/glustervolumes" rel="glustervolumes"/>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/affinitygroups" rel="affinitygroups"/>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/networkfilters" rel="networkfilters"/>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/networks" rel="networks"/>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/permissions" rel="permissions"/>
<link href="/ovirt-engine/api/clusters/65316857-7513-45a1-8183-57706fb8639c/cpuprofiles" rel="cpuprofiles"/>
<ballooning_enabled>false</ballooning_enabled>
<cpu>
<architecture>x86_64</architecture>
<type>Intel Conroe Family</type>
</cpu>
<custom_scheduling_policy_properties>
<property>
<name>HighUtilization</name>
<value>75</value>
</property>
<property>
<name>CpuOverCommitDurationMinutes</name>
<value>1</value>
</property>
<property>
<name>HeSparesCount</name>
<value>0</value>
</property>
</custom_scheduling_policy_properties>

Comment 1 Oved Ourfali 2017-07-02 12:37:35 UTC
If the properties appear in the rest api, then it isn't an api issue. 
Moving to sla to check why the ui isn't showing that.

Comment 2 Doron Fediuck 2017-07-05 09:38:52 UTC
Can you be more specific on what properties you're referring to?
What is the expected result?

Comment 3 Nelly Credi 2017-07-05 10:02:47 UTC
<property>
<name>HighUtilization</name>
<value>75</value>
</property>
<property>
<name>CpuOverCommitDurationMinutes</name>
<value>1</value>
</property>

they appear in the object when querying via the api.
i would expect it to be filled in the UI when I create the object,
otherwise if ill try to edit the cluster in the ui, 
ill get an error that these fields are empty

Comment 4 Doron Fediuck 2017-07-05 10:10:01 UTC
(In reply to Nelly Credi from comment #3)
> <property>
> <name>HighUtilization</name>
> <value>75</value>
> </property>
> <property>
> <name>CpuOverCommitDurationMinutes</name>
> <value>1</value>
> </property>
> 
> they appear in the object when querying via the api.
> i would expect it to be filled in the UI when I create the object,
> otherwise if ill try to edit the cluster in the ui, 
> ill get an error that these fields are empty

If you refresh the screen will it show up?

Comment 5 Nelly Credi 2017-07-05 10:19:36 UTC
no

Comment 6 Martin Sivák 2017-07-18 15:43:31 UTC
*** Bug 1464763 has been marked as a duplicate of this bug. ***

Comment 13 Artyom 2017-07-20 07:11:39 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20170718165351.gita56ecd5.el7.centos.noarch

1) Create new cluster via REST
<cluster>
<name>test</name>
<cpu>
<architecture>x86_64</architecture>
<type>Intel Conroe Family</type>
</cpu>
<version>
<major>4</major>
<minor>2</minor>
</version>
<data_center id="58cfb470-02f3-03d7-0386-0000000003bc"/>
</cluster>
2) Check scheduling policy parameters via UI, parameters exist
3) Update cluster name only, succeeded

Comment 15 Sandro Bonazzola 2017-12-20 10:56:02 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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