Bug 1034411 - BatchUpdateException on bundle deployment
Summary: BatchUpdateException on bundle deployment
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Provisioning
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: JON 3.2.2
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 19:14 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-02-26 13:58:22 UTC
Type: Bug


Attachments (Terms of Use)
bundle.log (5.92 KB, text/x-log)
2014-02-26 13:55 UTC, Armine Hovsepyan
no flags Details

Description Armine Hovsepyan 2013-11-25 19:14:11 UTC
Description of problem:
BatchUpdateException on bundle deployment

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

How reproducible:
1 out of 5

Steps to Reproduce:
1. navigate to bundles
2. upload bundle version 1.1
3. deploy bundle version 1.1 to destination1
4. upload same bundle version 1.2
5. deploy bundle version 1.2 to destination2

Actual results:
exception in log -> http://d.pr/f/VNe4
deployment fails

Expected results:
deployment passes, no exception in logs

Additional info:

Comment 1 John Mazzitelli 2014-02-25 16:51:39 UTC
Need more details, Armine.

I just tried this and it all worked for me.

Here is what I did:

1) create "group1" with a single "platform" resource in it
2) create "bundle 1"
3) deploy "bundle 1" to "destination 1" which has "group1" associated with it and the target directory was "/tmp/deleteme/bundle"
4) create "bundle 2"
5) deploy "bundle 2" to new "destination 2" which also had "group1" associated with it but its target directory was "/tmp/deleteme/another"

I verified the bundle content is correct in both places - /tmp/deleteme/bundle and /tmp/deleteme/another

Comment 2 Armine Hovsepyan 2014-02-26 13:55:49 UTC
Created attachment 868029 [details]
bundle.log

Attached are fragments from server and agent logs - i am not hitting the initial exception as well.

Bug can be closed as "works for me", as not reproducible anymore. In case of hitting the same bug again will reopen this bug.


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