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

Bug 2087768

Summary:	Verify backup disk size before triggering backup task in the spoke
Product:	OpenShift Container Platform	Reporter:	sahasan
Component:	Telco Edge	Assignee:	sahasan
Telco Edge sub component:	TALO	QA Contact:	Joshua Clark <josclark>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	ijolliff, jun, keyoung, nparekh, openshift-bugzilla-robot
Version:	4.11	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.11.0
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:	2022-08-18 04:08:08 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:	2093001

Description sahasan 2022-05-18 13:17:12 UTC

Description of problem:


Currently the backup disk size is not estimated, in case disk space is limited, the backup task triggered by TALO will fail.


How reproducible:
If a backup task require more than the disk space is available.


Expected results:
- verify the disk space required vs available to ensure backup task can be triggered.
- if the disk space is limited, return backup can't be started and the reason in the operator level status, which will prevent from triggering a failed job in the spoke

Additional info:

Comment 1 sahasan 2022-06-08 12:28:18 UTC

The PR has been merged which successfully estimate and verify backup size

Comment 2 sahasan 2022-06-08 14:48:59 UTC

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

Comment 3 Joshua Clark 2022-07-07 13:34:57 UTC

Both test cases passed in 4.11 QE. Verified.

Comment 6 errata-xmlrpc 2022-08-18 04:08:08 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.11 CNF vRAN extras update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHEA-2022:6110