Bug 1783751 - Block upgrade if there's a risk of running out of space (say, any brick / volume is @ >90% full capacity)
Summary: Block upgrade if there's a risk of running out of space (say, any brick / vol...
Keywords:
Status: CLOSED DUPLICATE of bug 1783750
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: unclassified
Version: rhhiv-1.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-15 09:43 UTC by Yaniv Kaul
Modified: 2019-12-31 07:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-28 16:13:52 UTC
Embargoed:
ykaul: needinfo+

Attachments (Terms of Use)

Description Yaniv Kaul 2019-12-15 09:43:14 UTC 
Description of problem:
We should ensure when upgrading that there's enough space before upgrading. You really don't want to run out of space in the middle of upgrade.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Sahina Bose 2019-12-27 06:01:37 UTC 
(In reply to Yaniv Kaul from comment #0)
> Description of problem:
> We should ensure when upgrading that there's enough space before upgrading.
> You really don't want to run out of space in the middle of upgrade.

Is this done if upgrade is done via ansible or UI (for instance, RHV-M)
Or do you mean to block for manual upgrade process too - not sure how feasible that is.

> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.
> 2.
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:
Comment 4 Yaniv Kaul 2019-12-28 16:13:52 UTC 

*** This bug has been marked as a duplicate of bug 1783750 ***
Note You need to log in before you can comment on or make changes to this bug.