Bug 1762709

Summary: OSTree - "Not such file or directory" error after Silverblue install and reboot
Product: [Fedora] Fedora Reporter: Éric Fintzel <efintzel>
Component: ostreeAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: dustymabe, hannsj_uhl, jonathan, miabbott, walters
Target Milestone: ---   
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 19:03:04 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:    
Bug Blocks: 1071880    
Attachments:
Description Flags
Screenshot before boot
none
Screenshot during boot none

Description Éric Fintzel 2019-10-17 10:03:40 UTC 
Description of problem:
After Silverblue installation and reboot a "No such file or directory" error is raised by ostree-prepare-root.

Reported with the Fedora-31-20191016.n.0 image but also occured with the Fedora-31-20191014.n.0 one.
Note the test is successful with the  Fedora-31-20191012.n.0 image.
Comment 1 Éric Fintzel 2019-10-17 10:11:32 UTC 
Created attachment 1626767 [details]
Screenshot before boot
Comment 2 Éric Fintzel 2019-10-17 10:13:29 UTC 
Created attachment 1626768 [details]
Screenshot during boot
Comment 3 Ben Cotton 2020-11-03 15:39:50 UTC 
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 4 Ben Cotton 2020-11-24 19:03:04 UTC 
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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
bug.

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