Bug 1019807 - AsyncResourceDeleteJob exception while re-deploying storage node
Summary: AsyncResourceDeleteJob exception while re-deploying storage node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Core Server, Storage Node
Version: JON 3.2
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ER07
: JON 3.2.0
Assignee: John Sanda
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 1002210 1012435
TreeView+ depends on / blocked
 
Reported: 2013-10-16 12:48 UTC by Armine Hovsepyan
Modified: 2015-09-03 00:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-02 20:34:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server.log (10.54 KB, text/x-log)
2013-10-16 12:48 UTC, Armine Hovsepyan
no flags Details
server.log(part) (31.81 KB, text/x-log)
2013-11-22 13:41 UTC, Armine Hovsepyan
no flags Details

Description Armine Hovsepyan 2013-10-16 12:48:50 UTC
Created attachment 812904 [details]
server.log

Description of problem:
AsyncResourceDeleteJob exception while re-deploying storage node

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

How reproducible:
2 out of 2

Steps to Reproduce:
1. install and start server with storage and agent on IP1
2. install and start storage and agent on IP2, connect to IP1
3. undeploy storage on IP2
4. re-deploy storage on IP2

Actual results:
AsyncResourceDeleteJob exception while re-deploying storage node in server.log

Expected results:
storage node is installed without exceptions in logs

Additional info:
fragment from server.log attached

Comment 1 Mike Foley 2013-11-11 16:35:16 UTC
JON 3.2 blocker per BZ Triage 11/11 ... santos, loleary, heute, yarboro, foley

Comment 2 John Sanda 2013-11-11 16:51:08 UTC
On what version did this occur?

Comment 3 John Sanda 2013-11-11 16:53:21 UTC
Disregard comment 2. I see that it was tested with ER3.

Comment 4 John Sanda 2013-11-11 17:22:45 UTC
I tested with a master build and did not reproduce, so hopefully whatever the issue is/was has already been fixed. Armine would you mind testing with a master build so we can verify whether or not any additional changes are needed for ER6?

Comment 5 Armine Hovsepyan 2013-11-12 10:17:26 UTC
Tested on master. The issue is not visible anymore. I guess issue has been fixed with the fixes under "Too Many exceptions" corresponding issues.

Comment 6 Thomas Heute 2013-11-12 10:59:44 UTC
Changed to MODIFIED so that it can be tested in ER6 again (rather than master)

Comment 7 Simeon Pinder 2013-11-19 15:48:45 UTC
Moving to ON_QA as available for testing with new brew build.

Comment 8 Simeon Pinder 2013-11-22 05:14:13 UTC
Mass moving all of these from ER6 to target milestone ER07 since the ER6 build was bad and QE was halted for the same reason.

Comment 9 Armine Hovsepyan 2013-11-22 13:41:34 UTC
Created attachment 827784 [details]
server.log(part)

Comment 10 Armine Hovsepyan 2013-11-22 13:42:23 UTC
verified in er7 (fragment from server.log attached)


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