Bug 750895 - Unable to detach drift definition from template in UI
Summary: Unable to detach drift definition from template in UI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: drift
Version: 4.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: JON 3.0.0
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 707225 749899
TreeView+ depends on / blocked
 
Reported: 2011-11-02 18:04 UTC by John Sanda
Modified: 2012-02-07 19:27 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2011-11-02 18:04:19 UTC
Description of problem:
If you go to edit a resource drift definition and set the 'Attached to Template' field to no, the change is not persisted in the database. Consequently, you are not able to detach a definition from the template from which it originated.

It is possible however to detach through the CLI. The problem though is not in in the UI. It just manifests itself in the UI because of the method calls made in the UI to apply the update to underlying DriftDefinition object.

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


How reproducible:
Always

Steps to Reproduce:
1. Go to create or edit a resource drift definition
2. Set the 'Attached to Template' field to no (i.e., false)
3. Save the change
   
Actual results:
The definition is still attached in the database.

Expected results:
The definition should be detached.

Additional info:
The problem is in DriftDefinition.setConfiguration. This is method called to actually update the definition in the UI. When I added the attached flag, I forgot to update the setConfiguration method to update the attached property along with the other properties that are updated in this method.

Comment 1 John Sanda 2011-11-02 19:25:15 UTC
Updating DriftDefinition to update its attached field when the underlying configuration is updated.

master branch commit hash:  1eb5ab398ad4c37cee6aed9c069cb1887a1fe2b2
release_jon3.x commit hash: 8955805230d595349a578326ff570946e96a80fd

Comment 2 Mike Foley 2011-11-03 18:44:18 UTC
verified build #684

Comment 3 Mike Foley 2012-02-07 19:26:14 UTC
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE

Comment 4 Mike Foley 2012-02-07 19:27:46 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


Note You need to log in before you can comment on or make changes to this bug.