Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1814966

Summary:	Block upgrade if there's a risk of running out of space (say, any brick / volume is @ >90% full capacity)
Product:	[oVirt] ovirt-engine	Reporter:	Gobinda Das <godas>
Component:	BLL.Gluster	Assignee:	Ritesh Chikatwar <rchikatw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4.0	CC:	bugs, mpandey, rchikatw, rhs-bugs, sabose, sasundar, ykaul
Target Milestone:	ovirt-4.4.0	Keywords:	ZStream
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+ godas: devel_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine 4.4.0-26 b5b5c99ca2f	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1783750	Environment:
Last Closed:	2020-08-05 06:10:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1783750

Description Gobinda Das 2020-03-19 07:20:56 UTC

Description of problem:
We should strive not to upgrade while we are near full capacity, as during the upgrade we might run out of capacity.
We can set it at 90% or 95% or whatnot, but still - very high capacity and running out of space at this point is a bit dangerous.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Comment 1 Gobinda Das 2020-03-19 11:40:21 UTC

*** Bug 1625148 has been marked as a duplicate of this bug. ***

Comment 2 SATHEESARAN 2020-07-15 19:06:47 UTC

Verified with RHV manager version 4.4.1, when the used space of the storage domain is above 90%, upgrade cluster 
initiated from RHV Manager UI fails with error "Cluster Default upgrade failed. Host disk is running low space on gluster volume(s): vmstore."

Comment 3 Sandro Bonazzola 2020-08-05 06:10:04 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.