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 1937940 - F34 SoaS disk images are missing initial-setp-gui
Summary: F34 SoaS disk images are missing initial-setp-gui
Alias: None
Product: Fedora
Classification: Fedora
Component: spin-kickstarts
Version: 34
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Václav Pavlín
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: ARMTracker F34BetaFreezeException
TreeView+ depends on / blocked
Reported: 2021-03-11 18:45 UTC by Paul Whalen
Modified: 2021-03-23 17:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-03-23 17:12:12 UTC
Type: Bug

Attachments (Terms of Use)

Description Paul Whalen 2021-03-11 18:45:25 UTC
Description of problem:

F34 SoaS ARM and AArch64 disk images are missing initial-setup-gui and instead boot to initial-setup-tui. 

PR - to add -

Comment 1 Paul Whalen 2021-03-11 18:46:57 UTC
Requesting FE for F34 Beta inclusion.

Comment 2 Ben Williams 2021-03-11 19:09:12 UTC
+1 FE

Comment 3 Adam Williamson 2021-03-11 19:18:15 UTC
Votes go to the Pagure ticket these days, not the bug. If it's not created yet it will be shortly.

Comment 4 Adam Williamson 2021-03-12 23:39:35 UTC
+3 in , marking accepted.

Comment 5 Adam Williamson 2021-03-13 00:25:28 UTC
I merged the PR for this, it should be resolved in the next compose (though in fact, why did we add it to fedora-kickstarts and not to the SoaS group in comps?) Please test and confirm.

Comment 6 Adam Williamson 2021-03-23 16:25:09 UTC
Paul, can you confirm this was fixed in Beta? Thanks.

Comment 7 Paul Whalen 2021-03-23 17:12:12 UTC
(In reply to Adam Williamson from comment #6)
> Paul, can you confirm this was fixed in Beta? Thanks.

Confirmed, fixed in Beta.

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