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:
mass add of key word FutureFeature to help track
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.
this seems to be resoloved. commit is working for old & new resources. moving to on_qa
Verified on master build. moving to verified. http://10.16.120.69:7080/
Mass-closure of verified bugs against JON.