Bug 2104582

Summary:	satellite disk filling up when using the bootdisk method to provision new servers
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Bootdisk Plugin	Assignee:	Leos Stejskal <lstejska>
Status:	CLOSED ERRATA	QA Contact:	sganar
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.10.7	CC:	ahumbe, fperalta, gtalreja, inecas, lstejska, lzap, rlavi, saydas, sshtein
Target Milestone:	6.15.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-23 17:12: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:

Description Waldirio M Pinheiro 2022-07-06 16:22:11 UTC

Description of problem:
When using the bootdisk method, satellite is filling up the "/run" filesystem, which means memory.

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


How reproducible:
100%

Steps to Reproduce:
1. Install satellite 6.10.z
2. Configure the compute resource (vcenter)
3. Create virtual machines using the bootdisk method
---
hammer host create --name server01 --hostgroup-id 24 --organization RedHat --location GSS --compute-attributes start=1 --provision-method="bootdisk" 
---

Actual results:
After a while, Satellite will complain about disk space
---
2022-06-30T14:02:23 [W|app|c774c5ac] Failed to generate ISO image for instance server01.lab.eng.rdu2.redhat.com: No space left on device @ io_write - /usr/share/foreman/tmp/bootdisk-iso-20220630-20313-1jbmubz/build/BOOT/EOS_KICKSTART_8_0_28_VMLINUZ
---

Expected results:
Should be able to keep going and create tons of servers

Additional info:

Comment 5 Leos Stejskal 2023-03-30 10:19:41 UTC

Hi,
yes this has been fixed [0] in foreman_bootdisk 19.0.4, which is available in Satellite 6.11.

[0] https://github.com/theforeman/foreman_bootdisk/commit/6276369809bdae2b6e9f07c7bd92a75417c976ef

Comment 7 Marek Hulan 2023-12-21 18:30:07 UTC

This seems like resolved long time ago, should this be closed as CURRENTRELEASE? 6.11 is out for a long time and older releases are end of life.

Comment 8 Leos Stejskal 2023-12-22 10:15:10 UTC

Yes you are correct, I will pass it to QAs to verify it on the stream and then we can close it.

Comment 12 sganar 2024-01-11 07:33:52 UTC

Verified.

Tested on Satellite 6.15.0 Snap 6.0

Steps followed: 
1. Configure a Satellite for provisioning.
2. Create a VMware CR
3. Create a host with VMware CR using the bootdisk method.

Observation: 
The host is provisioned successfully and there is no issue regarding disk space.
This has been tested on Vmware 7 and Vmware 8

Comment 15 errata-xmlrpc 2024-04-23 17:12: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 (Important: Satellite 6.15.0 release), 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-2024:2010