Bug 1058703

Summary:	Cluster custom properties are not update through webadmin
Product:	[Retired] oVirt	Reporter:	Tal Nisan <tnisan>
Component:	ovirt-engine-core	Assignee:	Gilad Chaplik <gchaplik>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	acathrow, ahadas, dfediuck, gchaplik, gklein, iheim, tnisan, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-03 10:04:54 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 Tal Nisan 2014-01-28 11:46:39 UTC

Description of problem:

When trying to update a cluster custom properties via webadmin, the cluster custom properties is not update in the DB and when trying to edit the cluster again the values return to default

How reproducible:

100%

Steps to Reproduce:
1. Via webadmin, go to "Clusters" tab, and edit an existing cluster
2. Click on "Cluster Policy" tab, edit the custom properties
3. Click "Ok"

Actual results:
Cluster custom properties were not update in the DB

Expected results:
Cluste custom properties should be updated in the DB

Additional info:
I debugged Jboss, it seems that the custom properties property on the VdsGroup in the UpdateVdsGroupCommand arrives as null so it's probably something around webadmin, most likely ClusterListModel

Comment 1 Sandro Bonazzola 2014-03-04 09:30:03 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 2 Gilad Chaplik 2014-03-21 00:34:44 UTC

that's odd, never saw it and I use it quite often, can you still reproduce in latest/3.4?

Comment 3 Sandro Bonazzola 2014-05-08 13:56:28 UTC

This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.