Bug 565490

Summary:	[raw-config]Existing config edits are failing to commit
Product:	[Other] RHQ Project	Reporter:	Preethi Thomas <pthomas>
Component:	Configuration	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	jsanda, whayutin
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.4	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 16:52:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	565635

Description Preethi Thomas 2010-02-15 13:25:38 UTC

Description of problem:
Changes made to the configs of already existing resources are failing to commit


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


How reproducible:


Steps to Reproduce:
1. Login to RHQ server with agent running
2. Select the Hosts/Postges resource
3. Click on the configure tab
4. Click on Edit
5. change a value and click commit
  
Actual results:

Configuration update request with id 0 failed. Component does not support the [org.rhq.core.pluginapi.configuration.ResourceConfigurationFacet] interface: ResourceContainer[resource=Resource[id=10019, type=Hosts File, key=/etc/hosts, name=Hosts File, parent=10-16-120-72.guest.rhq.lab.eng.bos.redhat.com]]

Expected results:

To be able to commit 

Additional info:

Comment 1 wes hayutin 2010-02-16 17:09:12 UTC

mass add of key word FutureFeature to help track

Comment 2 John Sanda 2010-02-16 19:50:20 UTC

When I ported code from the JSF backing to the new seam components, I forgot to port logic for calling the appropriate update method in ConfigurationManagerBean during a commit. It was calling a method that only supports the new api. I added back in a check to determine the correct api to call.

Comment 3 Preethi Thomas 2010-02-16 20:49:43 UTC

this seems to be resoloved. commit is working for old & new resources.
moving to on_qa

Comment 4 Preethi Thomas 2010-02-19 13:26:17 UTC

Verified on master build. moving to verified.
http://10.16.120.69:7080/

Comment 5 Corey Welton 2010-08-12 16:52:19 UTC

Mass-closure of verified bugs against JON.