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 bugzilla.redhat.com.
Bug 2091013 (F37Everythingbootaarch64Oversize) - Fedora 37: Everything boot aarch64 image exceeds maximum size
Summary: Fedora 37: Everything boot aarch64 image exceeds maximum size
Keywords:
Status: CLOSED ERRATA
Alias: F37Everythingbootaarch64Oversize
Product: Fedora
Classification: Fedora
Component: distribution
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aoife Moloney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FedoraOversizeTracker
TreeView+ depends on / blocked
 
Reported: 2022-05-27 10:40 UTC by Fedora QA Tools SIG
Modified: 2023-05-09 13:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-14 17:11:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Fedora QA Tools SIG 2022-05-27 10:40:29 UTC 
Everything boot aarch64 image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220527.n.0/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20220527.n.0.iso from compose Fedora-Rawhide-20220527.n.0 is 745428992 bytes, exceeding the maximum size 734003200. Canonical maximum sizes can be found at https://fedoraproject.org/wiki/Releases/37/Spins and https://fedoraproject.org/wiki/Releases/37/ReleaseBlocking . 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 https://pagure.io/fedora-qa/relval/issues 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 2022-06-11 00:11:35 UTC 
Everything boot aarch64 image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220610.n.1/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20220610.n.1.iso from compose Fedora-Rawhide-20220610.n.1 is 745971712 bytes, exceeding the maximum size 734003200.
Comment 2 Fedora QA Tools SIG 2022-06-14 09:08:21 UTC 
Everything boot aarch64 image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220614.n.0/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20220614.n.0.iso from compose Fedora-Rawhide-20220614.n.0 is 740659200 bytes, exceeding the maximum size 734003200.
Comment 3 Fedora QA Tools SIG 2022-06-17 16:00:12 UTC 
Everything boot aarch64 image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220617.n.0/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20220617.n.0.iso from compose Fedora-Rawhide-20220617.n.0 is 745773056 bytes, exceeding the maximum size 734003200.
Comment 4 Fedora QA Tools SIG 2022-06-22 03:32:31 UTC 
Everything boot aarch64 image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220621.n.3/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20220621.n.3.iso from compose Fedora-Rawhide-20220621.n.3 is 747010048 bytes, exceeding the maximum size 734003200.
Comment 5 Fedora QA Tools SIG 2022-06-28 09:55:11 UTC 
Everything boot aarch64 image https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220628.n.0/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20220628.n.0.iso from compose Fedora-Rawhide-20220628.n.0 is 742451200 bytes, exceeding the maximum size 734003200.
Comment 6 Ben Cotton 2022-08-09 13:38:50 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.
Comment 7 Adam Williamson 2022-12-14 17:11:10 UTC 
I think this actually got fixed along the way, or we'd have more reports.
Note You need to log in before you can comment on or make changes to this bug.