Bug 2052001

Summary: Fedora-Workstation-35-1.2.aarch64.raw at https://getfedora.org/en/workstation/download/ fails to boot (see Red Hat Bugzilla – Bug 2012496)
Product: [Fedora] Fedora Reporter: John Dodson <jwadodson>
Component: distributionAssignee: Aoife Moloney <amoloney>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: kevin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 16:36:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2012496    
Bug Blocks:    

Description John Dodson 2022-02-08 13:59:38 UTC
Description of problem:
Fedora-Workstation-35-1.2.aarch64.raw at https://getfedora.org/en/workstation/download/ fails to boot (see Red Hat Bugzilla – Bug 2012496)

Version-Release number of selected component (if applicable):

Fedora-Workstation-35-1.2.aarch64.raw

How reproducible:

Always

Steps to Reproduce:
1. Try booting that distribution on for example a Pi4
2.
3.

Actual results:
Boot fails (dracut)

Expected results:

Boot succeeds.

Additional info:

Comment 1 John Dodson 2022-02-08 14:00:17 UTC
Can we please have a new distro to replace 1.2?

Comment 2 Ben Cotton 2022-02-08 15:02:11 UTC
Does this affect hardware besides the Pi 4? The Pi 4 is officially unsupported, but if affects supported hardware, I'll see what we can do. We normally don't respin installation media after the release.

Comment 3 John Dodson 2022-02-09 02:31:41 UTC
Thanks Ben,
Sadly I don't have other Pi's I can test it on (can't take them out of service) but the
Fedora-Workstation-35-1.1.aarch64.raw did boot on the 4.

Then once upgraded (via dnf) it failed to boot due to the bug referenced above.

Later I went back to try the new "distro" (Fedora-Workstation-35-1.2.aarch64.raw) & it failed
to boot, as it appeared that the bug referenced above had now been introduced into it.

So I think the answer is probably yes because the problem is related to UUID used during boot
which was "munged" in the dracut later version.

Obviously there was an impetus to create the "1.2" version of the distro, if it was due to the
dracut changes then that's pretty sad!

I see FC36 will release on 2022-04-19 - long time to wait - 2 months.
How long would a respin take? officially?

Alternatively is the Fedora-Workstation-35-1.1.aarch64.raw version still available anywhere?
(The Aust/AARNet mirror seems not to have it)
I can't seem to find it elsewhere by searching for "it" ("Fedora-Workstation-35-1.1.aarch64.raw.xz")

Comment 4 John Dodson 2022-02-09 02:32:56 UTC
Is the Pi4 expected to be "officailly supported" soon?

Comment 5 Ben Cotton 2022-11-29 17:51:05 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-12-13 16:36:33 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.