Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1921687 (F34Serverbootaarch64Oversize) - Fedora 34: Server boot aarch64 image exceeds maximum size
Summary: Fedora 34: Server boot aarch64 image exceeds maximum size
Alias: F34Serverbootaarch64Oversize
Product: Fedora
Classification: Fedora
Component: distribution
Version: 34
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Aoife Moloney
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F34BetaBlocker
TreeView+ depends on / blocked
Reported: 2021-01-28 12:28 UTC by Fedora QA Tools SIG
Modified: 2023-05-09 13:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-12 21:42:33 UTC
Type: ---

Attachments (Terms of Use)

Description Fedora QA Tools SIG 2021-01-28 12:28:32 UTC
Server boot aarch64 image from compose Fedora-Rawhide-20210128.n.0 is 738613248 bytes, exceeding the maximum size 734003200. Canonical maximum sizes can be found at and . This check is run by the 'relval' tool, which has its own list of maximum sizes derived from those pages. If the maximum size used for this comparison is wrong, please add a comment and file a bug against relval at and it will be corrected. If you believe the canonical maximum size for an image should be changed, please follow the appropriate process before filing a relval bug.

Comment 1 Fedora QA Tools SIG 2021-01-31 10:56:52 UTC
Server boot aarch64 image from compose Fedora-Rawhide-20210131.n.0 is 739395584 bytes, exceeding the maximum size 734003200.

Comment 2 Ben Cotton 2021-02-09 15:44:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 3 Adam Williamson 2021-02-12 21:42:33 UTC
This was to do with debug kernels as discussed in 1921687 and has been fixed for a while. Closing.

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