Bug 1416097

Summary: Failed to delete the bundles when deleting a bundle with lot of configuration parameters and versions
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: Database, PerformanceAssignee: Josejulio Martínez <jmartine>
Status: CLOSED ERRATA QA Contact: Jeeva Kandasamy <jkandasa>
Severity: medium Docs Contact:
Priority: medium    
Version: JON 3.3.8CC: jkandasa, jmartine, spinder
Target Milestone: DR01Keywords: Triaged
Target Release: JON 3.3.9   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-02 17:21:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
test bundle
none
verified screenshot none

Description Filip Brychta 2017-01-24 15:15:36 UTC
Created attachment 1243948 [details]
test bundle

Description of problem:
When having a lot of configuration parameters defined in deploy.xml and after a certain number of uploaded bundle versions it takes long time to delete that bundle. It is eventually deleted but err msg 'Failed to delete the bundles' is shown.

Version-Release number of selected component (if applicable):
JON3.3.8.ER01

How reproducible:
2/2

Steps to Reproduce:
1. Create new bundle ( use attached test2.zip )
2. In the deploy.xml change the version number, create new bundle and upload it to the JBoss ON;
3. Repeat step 2 for 10 different bundle versions;
4. Remove the bundle

Actual results:
Failed to delete the bundles - A request timeout has expired after 30000 ms
The bundle is eventually deleted but it takes several minutes (~ 6 minutes in my case)

Expected results:
Error msg should be shown only when the delete operation actually fails. When it takes long time it should not be displayed as failure.

Additional info:
Found when deleting bundle created via repro steps from BZ1399125

Comment 1 Josejulio Martínez 2017-08-16 22:33:06 UTC
commit ae8a9677cb345ad62a41fce331f37d467d650c5e
Merge: 95eea35 1368686
Author: Michael Burman <yak>
Date:   Wed Aug 16 16:32:09 2017 +0300

    Merge pull request #311 from josejulio/bugs/1416097
    
    Bug 1416097 - Failed to delete the bundles when deleting a bundle wit…

commit 136868674135fb3fb6401384f4c84ed49c13c148
Author: Josejulio Martínez <jmartine>
Date:   Wed Aug 2 11:40:40 2017 -0500

    Updates view_bundle_list_deleteTakesLongDetail message


commit c7f7a902cefc637f45ff977b20e6fd067575bc82
Author: Josejulio Martínez <jmartine>
Date:   Wed Aug 2 10:38:04 2017 -0500

    Bug 1416097 - Failed to delete the bundles when deleting a bundle with lot of configuration parameters and versions
     Added an INFO message telling it takes long to delete a bundle with many parameters and versions.

Comment 3 Simeon Pinder 2017-09-01 15:34:01 UTC
Moving to ON_QA as available for test with the following binary:
http://download.eng.bos.redhat.com/brewroot/packages/org.jboss.on-jboss-on-parent/3.3.0.GA/133/maven/org/jboss/on/jon-server-patch/3.3.0.GA/jon-server-patch-3.3.0.GA.zip

*NOTE Build represents JON 3.3.9 DR01 build.

Please report issues as you encounter them.

Comment 4 Jeeva Kandasamy 2017-09-06 07:16:43 UTC
Created attachment 1322523 [details]
verified screenshot

Works as mentioned on the fix. Shows INFO message "A request to delete the selected bundles is taking too long". Screenshot is attached.


Version info:
-------------

OS: Fedora 26
Browser: Firefox 55.0.2 (64-bit)

JBoss Operations Network	
Version: 3.3.0.GA Update 09
Build Number: 74b22f5:8c38c0a
GWT Version: 2.5.0
SmartGWT Version: 3.0p

Comment 5 errata-xmlrpc 2017-10-02 17:21:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:2846