Bug 2119992

Summary: Updates rolled back on boot
Product: [Fedora] Fedora Reporter: Daan Vanoverloop <daan>
Component: IoTAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36   
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 18:20:17 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:
Attachments:
Description Flags
Output of journalctl -b none

Description Daan Vanoverloop 2022-08-20 17:38:56 UTC 
Created attachment 1906656 [details]
Output of journalctl -b

Description of problem:

Each time I try to update the system, it rolls back during boot and the latest deployment is removed. As a result, I am unable to update the system or layer additional packages.

How reproducible:

Not sure if this can be reproduced on a clean install, but to reproduce you would have to run `rpm-ostree update`. A new deployment will be staged, but after rebooting this deployment will be gone, and it has booted on the previous one.

Actual results:

I am still on 36.20220810.0 after updating.

```
Deployments:
● fedora-iot:fedora/stable/aarch64/iot
                  Version: 36.20220810.0 (2022-08-10T10:07:03Z)
               BaseCommit: a85cfdf27e196481f6071a7602341015605d8d123f36dfd1094b4d8bc543c35b
             GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
          LayeredPackages: cockpit-networkmanager cockpit-ostree cockpit-pcp cockpit-podman cockpit-selinux cockpit-system cockpit-ws docker-compose fail2ban git man man-pages neovim net-tools podman-docker
                           postfix wget wireguard-tools zsh

  fedora-iot:fedora/stable/aarch64/iot
                  Version: 36.20220807.0 (2022-08-07T16:53:19Z)
               BaseCommit: d27e34e7fc7d45743b524348221a6cf37996bbaca8aca3d36e3af33734d05b8d
             GPGSignature: Valid signature by 53DED2CB922D8B8D9E63FD18999F7CBF38AB71F4
          LayeredPackages: cockpit-networkmanager cockpit-ostree cockpit-pcp cockpit-podman cockpit-selinux cockpit-system cockpit-ws docker-compose fail2ban git man man-pages neovim net-tools podman-docker
                           postfix wget wireguard-tools zsh
```

Expected results:

I expected it to boot on the latest deployment it had staged after updating.

Additional info:

I am running on a Raspberry PI 4 model B. I believe this issue might be related to the system clock being wrong initially when booting, as seen in the journal file I have attached. Despite it saying 14 July, it is actually a log from today.

Possibly related to this issue: https://bugzilla.redhat.com/show_bug.cgi?id=2042665
Comment 1 Peter Robinson 2022-08-23 08:49:47 UTC 
> I am running on a Raspberry PI 4 model B. I believe this issue might be
> related to the system clock being wrong initially when booting, as seen in
> the journal file I have attached. Despite it saying 14 July, it is actually
> a log from today.

Shouldn't make any difference, I run it on rpi devices without battery backed RTCs

> Possibly related to this issue:
> https://bugzilla.redhat.com/show_bug.cgi?id=2042665

Do you depend on DNSSEC or other things that are time dependent?
Comment 2 Daan Vanoverloop 2022-08-23 11:27:59 UTC 
> Do you depend on DNSSEC or other things that are time dependent?

Not that I'm aware of. I've been doing automatic updates for about a year now without issues, but now I suddenly noticed it hadn't updated in a while, and I am unable to update manually. I did not change the configuration of the system in any meaningful way, I only run some podman containers.
Comment 3 Ben Cotton 2023-04-25 17:48:07 UTC 
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 4 Ludek Smid 2023-05-25 18:20:17 UTC 
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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.