Bug 2251847 - livecd-creator fails on latest Release of Rocky 8
Summary: livecd-creator fails on latest Release of Rocky 8
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: livecd-tools
Version: epel8
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-11-28 04:11 UTC by Len E.
Modified: 2023-12-03 16:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
Text of the subject post on the Rocky user forum (8.63 KB, application/rtf)
2023-11-28 04:11 UTC, Len E.
no flags Details

Description Len E. 2023-11-28 04:11:15 UTC
Created attachment 2001779 [details]
Text of the subject post on the Rocky user forum

Description of problem:
livecd-creator, when processing a Rocky 8 kickstart file, aborts with
mksquashsf error near the end of a normal run, on Rocky 8.9.
The run completes normally without a problem on Rocky 8.8.

Version-Release number of selected component (if applicable):
version 31.0-1.el8

How reproducible:  Reproducible with any normal Rocky kickstart.


Steps to Reproduce:
1. Download one of the standard Rocky kickstart files
2. Substitute the repositories on a test machine (eg with CentOS 8 stream)
   for the Rocky repositories.
3. Run livecd-creator

Actual results:


Expected results:


Additional info:

Comment 1 Len E. 2023-12-03 16:41:36 UTC
I now believe the problem was caused simply by a lack of disk space.
The messages from the livecd-creator run showed that 6144MB was being
used for cache space.
The partition size for the run was 15GB, and the df command at
the start of the run indicated only ~5500MB unused space was
available.  (There was a 4GB swap partition enabled).
I've rerun the livecd-creator session in a 25GB partition, and
it has completed normally.

Len E.


Note You need to log in before you can comment on or make changes to this bug.