Bug 1855116

Summary:	Unable to reboot AND rollback after upgrade to 32.20200702.0 on MacBook Pro
Product:	[Fedora] Fedora	Reporter:	Adam Kaplan <adam.kaplan>
Component:	rpm-ostree	Assignee:	Colin Walters <walters>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	32	CC:	dustymabe, jlebon, jonathan, miabbott, philip.wyett, sdodson, walters
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-25 17:11: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:

Description Adam Kaplan 2020-07-09 02:00:07 UTC

Description of problem:

After running `rpm-ostree deploy 32.20200702.0` on a MacBook Pro (with dual EFI partitions), Fedora Silverblue fails to restart.

Attempt to use GRUB to rollback to 32.20200701.0 fails with following message:

```
APFSSTART:1584: Mounting with apfs_efi_osx-1412.101.1
efi_fusion_pairing:686: Container <sha>
efi_fusion_pairing:691: fusion uuid: <zeros>
efi_container_create:990: Volume attached is internal
nx_kernel_mount:1385: : checkpoint search: largest xid 5730425, best xid 5730425 @ 193
er_state_obj_get_for_recovery:4639: No ER state object for volume Preboot - rolling is not happening, nothing to recover.
er_state_obj_get_for_recovery:4639: No ER state object for volume Preboot - rolling is not happening, nothing to recover.
System BootOrder not found. Initializing defaults.
```

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


How reproducible: Always


Steps to Reproduce:
1. Partition a MacBook Pro to run Silverblue with version 32.20200701.0. Mine is a mid-2015 15" Retina model.
2. Run rpm-ostree deploy 32.20200702.0
3. Reboot

Actual results:

Computer does not reboot. Booting to GRUB displays the message above - changing the kernel and then running rpm-ostree rollback is not possible.

Expected results:

Upgrade is successful. Barring that, GRUB menu allows me to boot to a prior kernel version and run a rollback.

Additional info:

Comment 1 Adam Kaplan 2020-07-09 02:02:25 UTC

Note that the only way I could recover from this situation was to reinstall via a live-boot USB, pin my verison to 32.20200701.0, and restore my data from a backup.

Comment 2 Jonathan Lebon 2020-07-09 19:00:16 UTC

Might be unrelated, though an issue with the same final error message showed up yesterday too in Fedora CoreOS: https://github.com/coreos/fedora-coreos-tracker/issues/563.

Comment 3 Colin Walters 2020-07-13 23:46:18 UTC

I think this might be corruption of the ESP.  rpm-ostree doesn't touch the ESP (see https://github.com/coreos/bootupd ) but it is mounted by default and I think we've seen reports that simply mounting it can corrupt things in some cases.

Comment 4 Adam Kaplan 2020-07-19 00:47:10 UTC

On a whim I thought, "perhaps the two EFI partitions could be an issue" - so I went full steam ahead and wiped it out, installed Silverblue 32 from live USB, then upgraded to the latest in the fedora:32 branch. The initial APFSTART message disappears - after booting to GRUB all I see is "System BootOrder not found. Initializing defaults."

Comment 5 Fedora Program Management 2021-04-29 16:48:52 UTC

This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 6 Ben Cotton 2021-05-25 17:11:33 UTC

Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.