Bug 2351459 - F42 Server boot aarch64 image is oversize
Summary: F42 Server boot aarch64 image is oversize
Keywords:
Status: CLOSED DUPLICATE of bug 2352679
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aoife Moloney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F42FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2025-03-12 04:58 UTC by Kamil Páral
Modified: 2025-03-27 10:59 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-03-15 16:01:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kamil Páral 2025-03-12 04:58:07 UTC
Description of problem:

F42 Beta RC1.3 compose:

Everything boot aarch64, size 1005193216, max 1000000000
Server boot aarch64, size 1014702080, max 1000000000
SoaS live aarch64, size 1698033664, max 1000000000
Xfce live aarch64, size 2237693952, max 2000000000
SoaS live x86_64, size 1756985344, max 1000000000
Xfce live x86_64, size 2302875648, max 2000000000
Python_Classroom live aarch64, size 2299131904, max 2000000000
Scientific_KDE live aarch64, size 5062320128, max 5000000000
Astronomy_KDE live x86_64, size 4708800512, max 4000000000
Design_suite live x86_64, size 4287289344, max 4000000000
Python_Classroom live x86_64, size 2389876736, max 2000000000
Scientific_KDE live x86_64, size 5385205760, max 5000000000
Security live x86_64, size 2468605952, max 2000000000 

Out of those, just "Server boot aarch64" is *probably* release blocking. Unfortunately the F42 release-blocking deliverables page is missing [1] (CC amoloney), but I assume it should be the same as in F41 [2].

[1] https://docs.fedoraproject.org/en-US/releases/f42/blocking/
[2] https://docs.fedoraproject.org/en-US/releases/f41/blocking/



Version-Release number of selected component (if applicable):
https://kojipkgs.fedoraproject.org/compose/42/Fedora-42-20250311.0/compose/Server/aarch64/iso/Fedora-Server-netinst-aarch64-42_Beta-1.3.iso

Comment 1 Kamil Páral 2025-03-12 04:59:18 UTC
An automatic release blocker per our policy:
https://fedoraproject.org/wiki/Fedora_42_Beta_Release_Criteria#Image_size_requirements

Comment 2 Adam Williamson 2025-03-12 06:10:14 UTC
For the record, I looked into why we didn't get an automatic blocker bug for this. It seems the API key that relvalconsumer uses to report bugs has been banned for some reason. :/ I'm looking into it.

Comment 3 Kamil Páral 2025-03-12 07:59:26 UTC
(In reply to Kamil Páral from comment #1)
> An automatic release blocker per our policy:
> https://fedoraproject.org/wiki/
> Fedora_42_Beta_Release_Criteria#Image_size_requirements

After discussion with Adam, it looks possible to move this criterion from Beta to Final. It's in Beta historically because of optical media (you can't really use a "bigger CD/DVD"), we believe, but that time has passed - the max sizes no longer even reflect optical sizes anymore. The criterion is still useful for Final, because some groups want to have a max image size for their audience.

Comment 4 Adam Williamson 2025-03-12 22:20:12 UTC
Some max sizes are still based on optical media. Specifically, anything with max size 4.7 GB - that's the size of a standard DVD.

Comment 5 Kamil Páral 2025-03-14 09:31:28 UTC
Discussed at Go/No-Go meeting [1]:

!agreed 2351459 - waived to Fedora 42 Final under the 'last minute' justification. this was discovered late due to robot malfunctions. in the usual course of events we would have discovered this weeks ago and either squished the image a bit or just bumped the size limit. since this is not a very significant size limit - nobody in the meeting has seen a 1GB USB stick lately - we're comfortable waiving it

[1] https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-13/f42-beta-go-no-go-meeting.2025-03-13-17.02.log.html


Accepted as a Final blocker.

Comment 6 Adam Williamson 2025-03-15 16:01:01 UTC
Marking this as a dupe of the relval-created one; if we do it the other way around the bot will just keep making new ones.

*** This bug has been marked as a duplicate of bug 2352679 ***


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