Bug 1783751

Summary: Block upgrade if there's a risk of running out of space (say, any brick / volume is @ >90% full capacity)
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Yaniv Kaul <ykaul>
Component: unclassifiedAssignee: Sahina Bose <sabose>
Status: CLOSED DUPLICATE QA Contact: Rahul Hinduja <rhinduja>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.7CC: nchilaka, rhs-bugs, sabose, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: ---Flags: ykaul: needinfo+
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: 2019-12-28 16:13:52 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:

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 ***