Description of problem: Some resource types allow for uploading content that they are not fully backed by (i.e. their creation type is not content). For example Linux platforms can accept RPM files, JBossAS4/5 resources can accept jar files to be put in lib, etc. The first attempt at deploying such files through the resource's content tab succeeds, but any further attempt at doing so will fail with the user unable to even upload the content to deploy. Version-Release number of selected component (if applicable): 4.10.0 and onwards, caused by commit 863048e054750d0b35f69cdc83594928e5c2603e How reproducible: Steps to Reproduce: 1. Go to a linux platform resource 2. Go to Content/New subtab 3. Click "UPLOAD NEW PACKAGE" 4. Click "UPLOAD FILE..." 5. In the pop up window, click "Add..." 6. Select any file 7. Click "Upload" 8. The popup will close and the name of the uploaded file will appear next to the "UPLOAD FILE..." button 9. Click "Cancel" 10. Go to step 3 Actual results: The second attempt at uploading the file will fail with garbage in the upload popup. Expected results: repeated uploads work Additional info: This is a regression introduced by BZ 1000065. Note that the "Cancel" step can be replaced by actually finishing the upload and still any further attempts at uploading any new file will fail. I did not discover any other remedy to this situation but to actually RESTART the RHQ server (logging out and logging back in DOESN'T help). That is why I marked the severity as high. Also note that this bug is present in the JON 3.2.0 and onwards.
commit 76f9e174ed62be4742f35a91bd3e9aa02934a81e Author: Lukas Krejci <lkrejci> Date: Tue May 20 14:59:55 2014 +0200 [BZ 1099485] Fix JSF file upload popup for all upload locations
Bulk close of items fixed in RHQ 4.12 If you think this is not solved, then please open a *new* BZ and link to this one.