Red Hat Bugzilla – Bug 790098
Drift: Unchecking the 'File Changed' option in 'Category' drop-down in the carousel view displays Globally uncaught exception
Last modified: 2015-02-01 18:27:43 EST
+++ This bug was initially created as a clone of Bug #760105 +++
Description of problem:
Create a drift definition specifying the Base Directory where a file exists. Change the file and wait till snapshot 1 is created. In the carousel view, Uncheck the 'File Changed' option in 'Category' dropdown. it displays a Globally uncaught exception in UI and in message center. There is no error in server/agent log.
Please refer the attached stack trace in message center.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a text file on platform at some directory(Ex: Test.txt)
2. Login to RHQ and create a drift definition on inventoried platform specifying the base Directory where the file is created.
3. Wait till the initial snapshot gets created.
4. Edit and make some changes in the same text file on platform.
5. Wait till the Snapshot 1 gets created.
6. Navigate to the drift definition and click on the drift definition name link.
7. In the 'Category' drop-down, uncheck the 'File Changed' option.
8. It displays a 'Globally uncaught exception'.
Globally uncaught exception.
No exception should be displayed.
--- Additional comment from email@example.com on 2011-12-05 07:59:36 EST ---
Created attachment 540850 [details]
--- Additional comment from firstname.lastname@example.org on 2011-12-05 10:31:04 EST ---
--- Additional comment from email@example.com on 2011-12-05 11:15:34 EST ---
master commit be9d41a3a6e8be965b5d016bea666c38af29b31c
release_jon3.x commit 168ac7ba4dc74dfea2fef0bf8331cafdae6cf7fa
This had to do with the filtering leaving no eligible snapshots.
--- Additional comment from firstname.lastname@example.org on 2011-12-05 11:26:19 EST ---
qe is requesting a developer code review for this late change in jon 3
--- Additional comment from email@example.com on 2011-12-05 11:58:48 EST ---
My mistake, this was never pushed to the release_jon3.x branch.
--- Additional comment from firstname.lastname@example.org on 2011-12-07 07:08:59 EST ---
Verified in maser build#818 (Version: 4.3.0-SNAPSHOT Build Number: bf5446c)
Followed the steps and verified that unchecking the 'File Changed' option does not display any exception.
--- Additional comment from email@example.com on 2011-12-09 06:53:18 EST ---
Marking as verified.
--- Additional comment from firstname.lastname@example.org on 2011-12-09 06:54:12 EST ---
Marking as verified.
--- Additional comment from email@example.com on 2012-02-07 14:24:55 EST ---
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
--- Additional comment from firstname.lastname@example.org on 2012-02-07 14:25:17 EST ---
marking VERIFIED JON 3 bugs to CLOSED/CURRENTRELEASE
--- Additional comment from email@example.com on 2012-02-13 11:29:52 EST ---
Setting Target Release correctly
Cherry picked from master:
release/jon3.0.x commit: 63957050f668025e2284b9db58dd6ca863036f16
Ensure that filter settings that would eliminate all snapshots
do not cause a problem.
Moving to ON_QA for testing with JON 3.0.1.GA RC5 or better:
verified JON 3.01 RC5
Bulk closing of old issues in VERIFIED state.