Bug 820333 - cannot deploy a bundle with config whose previous deployment didn't have any config
Summary: cannot deploy a bundle with config whose previous deployment didn't have any ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: JON 3.1.1
Assignee: Armine Hovsepyan
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 818751
Blocks: 828838
TreeView+ depends on / blocked
 
Reported: 2012-05-09 16:22 UTC by Charles Crouch
Modified: 2015-09-03 00:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 818751
Environment:
Last Closed: 2013-09-03 15:06:53 UTC
Embargoed:

Attachments (Terms of Use)
bundleUpdate (116.70 KB, image/png)
2012-08-03 17:47 UTC, Armine Hovsepyan 		no flags Details
View All

Comment 1 Charles Crouch 2012-05-09 16:23:56 UTC 
Unless this is a regression I don't see it as a JON3.1 blocker so targeting to cherry pick this fix from master as part of JON3.1.1.
Comment 2 John Mazzitelli 2012-05-09 16:41:36 UTC 
(In reply to comment #1)
> Unless this is a regression I don't see it as a JON3.1 blocker so targeting to
> cherry pick this fix from master as part of JON3.1.1.

this is not a regression - its a bug that has been in there for a while.
Comment 3 John Mazzitelli 2012-06-20 15:08:55 UTC 
see bug 828843 (bug 828838) for a similar issue
Comment 4 John Mazzitelli 2012-07-18 16:11:08 UTC 
commit to release/jon3.1.x branch: 521552eacb1d0ecb0a317d8f593fcc785a56c190
Comment 5 John Sanda 2012-08-02 18:51:51 UTC 
JON 3.1.1 ER1 build is available. Moving to ON_QA.

https://brewweb.devel.redhat.com/buildinfo?buildID=226942
Comment 6 Armine Hovsepyan 2012-08-03 17:47:29 UTC 
Created attachment 602171 [details]
bundleUpdate

verified!

first bundle has just war and the second is the same war with property. Update has been done correctly.
Comment 7 Heiko W. Rupp 2013-09-03 15:06:53 UTC 
Bulk closing of old issues in VERIFIED state.
Note You need to log in before you can comment on or make changes to this bug.