Bug 2099277

Summary:	Nodes are required to have installation disks of at least 120GB instead of at minimum of 100GB
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Osher De Paz <odepaz>
Component:	Infrastructure Operator	Assignee:	Michael Filanov <mfilanov>
Status:	CLOSED ERRATA	QA Contact:	Chad Crum <ccrum>
Severity:	medium	Docs Contact:	Derek <dcadzow>
Priority:	unspecified
Version:	rhacm-2.6	CC:	cbynum, ccrum, trwest, yfirst
Target Milestone:	---	Flags:	cbynum: rhacm-2.6+ cbynum: rhacm-2.6.z+
Target Release:	rhacm-2.6
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-09-06 22:33:25 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:	2099270

Description Osher De Paz 2022-06-20 12:37:37 UTC

Description of the problem:
Currently assisted-installer requires all nodes (master/worker/SNO) to have a minimum of 120GB disk space in one of their disks to use as an installation disk. Since openshift version 4.6 the official requirements have been changed to 100GB (ocp<=4.5 still has it 120GB) so we should update the requirements as either way we allow installation of later OCP versions.

Release version:
Relevant to all 2.5.x versions currently available.

OCP version:
Relevant to all OCP versions currently supported

Steps to reproduce:
1. Try to install a cluster with nodes having a disk of 100GB
2. Take a look at hosts' state. It will display as insufficient with message that no disk is available for installation

Actual results:
Hosts are in "insufficient" state.

Expected results:
Hosts considered "ready" to participate in cluster installation.

Comment 1 Osher De Paz 2022-06-20 12:40:19 UTC

This one already fixed U/S, I guess there's no much ways to test if we don't have 2.6 builds yet (and iirc we don't have). So I'm moving it to verified in favor of having it really verified in 2.5 builds

Comment 4 errata-xmlrpc 2022-09-06 22:33:25 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 (Moderate: Red Hat Advanced Cluster Management 2.6.0 security updates and bug fixes), 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/RHSA-2022:6370