Bug 1077634 - Failed to update connection settings
Summary: Failed to update connection settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration
Version: 4.11
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: GA
: RHQ 4.11
Assignee: Jay Shaughnessy
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-18 10:42 UTC by Filip Brychta
Modified: 2014-07-21 10:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-21 10:13:35 UTC
Embargoed:

Attachments (Terms of Use)
server log (161.89 KB, text/x-log)
2014-03-18 10:42 UTC, Filip Brychta 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1073201 0 high CLOSED Agent does a discovery loop if the inventory contains an unknown resource 2021-02-22 00:41:40 UTC

Internal Links: 1073201

Description Filip Brychta 2014-03-18 10:42:28 UTC 
Created attachment 875868 [details]
server log

Description of problem:
Update of connection settings fails with following exception:
org.hibernate.PersistentObjectException:detached entity passed to persist: org.rhq.core.domain.configuration.definition.ConfigurationDefinition

Version-Release number of selected component (if applicable):
Version :	
4.11.0-SNAPSHOT
Build Number :	
65e78e6

How reproducible:
Always

Steps to Reproduce:
1. clean installation of rhq
2. import some platform
3. navigate to platform resource -> Inventory -> Connection Settings
4. update any filed (e.g Metadata Cache Timeout)
5. click on save button

Actual results:
Failed to update connection settings.
org.hibernate.PersistentObjectException:detached entity passed to persist: org.rhq.core.domain.configuration.definition.ConfigurationDefinition

Expected results:
No errors

Additional info:
Complete exception from server log attached.
Comment 1 Filip Brychta 2014-03-18 11:22:02 UTC 
This was discovered by automation. Last successful run was on rhq master fe43668
Comment 2 Jay Shaughnessy 2014-03-19 13:33:58 UTC 
This problem is not in any release, found and fixed during 4.11 development.

This BZ results from a regression due to changes for Bug 1073201. I will link the BZ's.

master commit ed149e572d7a063ad69d45a47aa97126180ebd4d
Author: Jay Shaughnessy <jshaughn>
Date:   Tue Mar 18 17:44:26 2014 -0400

[1073201] revision due to regression
When updating plugin config we added an optimization to root the ensuing
service discovery at the resource being updated, as opposed to doing a
full service scan.  The regression resulted from passing the attached
Resource to the agent.  Never pass attached objects to the agent from
the server.  Unfortunately, detaching the object was not viable as it
actually needed to stay attached for the overall logic flow. So, I
lightened the API to just require the resourceId, which is a better agent
API anyway.
Comment 3 Filip Brychta 2014-03-19 14:58:27 UTC 
Verified on
Version :	
4.11.0-SNAPSHOT
Build Number :	
978063b
Comment 4 Heiko W. Rupp 2014-07-21 10:13:35 UTC 
Bulk closing of RHQ 4.11 issues, now that RHQ 4.12 is out.

If you find an issue with those, please open a new BZ, linking to the old one.
Note You need to log in before you can comment on or make changes to this bug.