Bug 1299160

Summary: [GSS](6.4.z) patch apply not java.io.IOException: No space left on device is not specific
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: PatchingAssignee: Tomas Hofman <thofman>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.6CC: brian.stansberry, jason.greene, jawilson, jbilek, jdoyle, jtruhlar, kconner, msimka, msochure, olubyans, thofman
Target Milestone: CR1   
Target Release: EAP 6.4.11   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:09:40 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:
Bug Depends On:    
Bug Blocks: 1361648    

Description Brad Maxwell 2016-01-16 18:22:49 UTC 
Patch apply can fail if there is not enough free space, however the message does not indicate what device does not have any free space.  Users assume there is not enough free space on the drive where the JBoss install they are applying the patch to, however it appears this may or may not be the case.

Patch apply uses tmp space and if there is not enough tmp space it will fail with this message as well.  The message should be more explicit as to where there is no space so that the user knows which drive to check.

[disconnected /] patch apply /path/to/jboss-eap-6.2.4-patch.zip
java.io.IOException: No space left on device
Comment 2 Tomas Hofman 2016-01-19 13:53:17 UTC 
PR: https://github.com/jbossas/jboss-eap/pull/2684
Comment 3 Tomas Hofman 2016-01-19 14:21:58 UTC 
Wrong branch.

New PR: https://github.com/jbossas/jboss-eap/pull/2685
Comment 4 JBoss JIRA Server 2016-01-25 15:02:09 UTC 
Tomas Hofman <thofman> updated the status of jira JBEAP-2881 to Coding In Progress
Comment 5 Mike McCune 2016-03-28 23:39:55 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 6 JBoss JIRA Server 2016-06-14 11:38:12 UTC 
Jiri Pallich <jpallich> updated the status of jira JBEAP-2881 to Closed
Comment 7 Jiří Bílek 2016-09-27 15:46:29 UTC 
Verified with EAP 6.4.11.CP.CR1
Comment 8 Petr Penicka 2017-01-17 13:09:40 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.