Bug 1876938 - SOAS spin is failing on armhfp due to space issues on root
Summary: SOAS spin is failing on armhfp due to space issues on root
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: spin-kickstarts
Version: 33
Hardware: armhfp
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Václav Pavlín
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F33BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2020-09-08 14:45 UTC by Paul Whalen
Modified: 2020-09-14 12:53 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-14 12:53:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Whalen 2020-09-08 14:45:16 UTC
Description of problem:
SOAS spin is failing on armhfp due to space issues on root. 

DEBUG util.py:621:  Error Summary
DEBUG util.py:621:  -------------
DEBUG util.py:621:  Disk Requirements:
DEBUG util.py:621:     At least 115MB more space needed on the / filesystem.

Koji Task:

https://kojipkgs.fedoraproject.org/compose/branched/Fedora-33-20200908.n.0/logs/armhfp/liveimage-Fedora-SoaS-armhfp-33-20200908.n.0.armhfp.log

Comment 1 Peter Robinson 2020-09-11 13:34:51 UTC
This should slim it down by dropping old python2 activities and all the dependencies: https://pagure.io/fedora-comps/pull-request/531

Comment 2 Fedora Blocker Bugs Application 2020-09-11 13:36:13 UTC
Proposed as a Freeze Exception for 33-beta by Fedora user pbrobinson using the blocker tracking app because:

 SoaS isn't building because of the size. There's a comps change in this BZ to slim it down

Comment 3 Adam Williamson 2020-09-11 21:11:12 UTC
+3 in https://pagure.io/fedora-qa/blocker-review/issue/83 , marking accepted. We usually grant FEs for failure to build a non-blocking image.

Comment 4 Peter Robinson 2020-09-14 12:53:20 UTC
Combination of kickstart update to exclude a few bits strangely getting pulled in and comps update has resolved this.


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