Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1492053 - Installation of Workstation os-tree completed but boot failed on uefi
Summary: Installation of Workstation os-tree completed but boot failed on uefi
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 27
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-09-15 11:04 UTC by Dominic P Geevarghese
Modified: 2018-11-30 19:49 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 19:49:40 UTC
Type: Bug

Attachments (Terms of Use)
uefi-ostree-boot-failure screenshot (4.26 KB, image/png)
2017-09-15 11:04 UTC, Dominic P Geevarghese
no flags Details

Description Dominic P Geevarghese 2017-09-15 11:04:25 UTC
Created attachment 1326393 [details]
uefi-ostree-boot-failure screenshot

Description of problem:

WS os-tree installation completed successfully but boot failed at "Shim UEFI keymanagement" screen, looks like regression of 


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

Fedora-Workstation-ostree-x86_64-27-20170912.n.0.iso failed to boot on uEFI VM. 

How reproducible:


Steps to Reproduce:
1. Install WS OS-TREE - Fedora-Workstation-ostree-x86_64-27-20170912.n.0
2. On UEFI based VM, installation completed but boot failed.
3. stuck at "Shim UEFI Key management" screen attached

Actual results:

Installation completed but boot failed

Expected results:

should boot without error

Dominic Geevarghese

Comment 1 Ben Cotton 2018-11-27 17:03:47 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 Fedora  'version' of '27'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2018-11-30 19:49:40 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

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

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