Bug 1017775 - have to limit file size on plugins upload page
Summary: have to limit file size on plugins upload page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: UI
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: JON 3.3.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-10 13:33 UTC by Jeeva Kandasamy
Modified: 2014-08-29 21:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-29 21:00:44 UTC
Type: Bug


Attachments (Terms of Use)

Description Jeeva Kandasamy 2013-10-10 13:33:32 UTC
Description of problem:
Negative case: Currently there is no restrictions on file size on GUI plugins upload page. This might lead 100% usage of disk space if we upload a big file accidentally. We should handle this situation somehow on file size restriction or some other way.  

If I have JON server work-space space also on / (root) partition, might lead system to nonfunctional state if it reach 100% of disk usage.

example: 
[jenkins@rhel-vm-2 bin]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_rhelvm2-lv_root
                       21G   17G  3.1G  85% /
tmpfs                 939M     0  939M   0% /dev/shm
/dev/vda1             485M   32M  428M   7% /boot


Version-Release number of selected component (if applicable):
Version: 3.2.0.ER3
Build Number: c0742ed:cbad264
GWT Version: 2.5.0
SmartGWT Version: 3.0

How reproducible:
100%

Steps to Reproduce:
1. Navigate to "Administration-->Server Plugins"
2. Click on "Choose File"(Upload plugin), select a big file (eg: 5GB or more) file and upload it.
3. Check disk space

Comment 1 Simeon Pinder 2013-11-08 14:41:22 UTC
Moving to unspecified target milestone as only JON 3.2.0 'blockers'(https://url.corp.redhat.com/bz-jon32-blockers-list-notmodified-nodocs) will make it into subsequent builds after ER5.

Comment 4 Stefan Negrea 2014-08-29 21:00:44 UTC
If a user does what is described in the reproduction steps, then it is an operator error. Even though disk space is monitored it is close to impossible to know which disk to track for upload purposes.


Also, there are many ways users can prevent this (many features implemented): 
1) Monitor disk space manually via the UI
2) Setup alerts on disk space
3) Pre-plan and configure a large amount of space


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