Bug 2117888 - rpm-ostree stop updating - apparently a "Failed to start ostree-boot-complete.service - OSTree Complete Boot" issue
Summary: rpm-ostree stop updating - apparently a "Failed to start ostree-boot-complete...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm-ostree
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-12 12:10 UTC by Boricua
Modified: 2022-08-13 15:09 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-08-13 15:09:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl output (8.87 KB, text/plain)
2022-08-12 12:10 UTC, Boricua
no flags Details

Description Boricua 2022-08-12 12:10:53 UTC
Created attachment 1905145 [details]
journalctl output

Description of problem: rpm-ostree shows updates to install. After reboot, the updates are not applied. This happens with Software and from the terminal.


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


How reproducible: each time I try to update components of Silverblue 36.


Steps to Reproduce:
1.Reboot the system to apply updates (tried both from terminal and Software).
2.System reboots and shows a failed procedure, but it moves too fast to be ascertained.
3.The same updates appear ready to be applied, after a reboot aimed to apply them.

Actual results:
The system does not update rpm components. Flatpak applications are not affected and keep updating (tried both in terminal and Software.

Expected results:
A successful update of all components.

Additional info:
This issue started a couple of days ago, after I tried to update Mailspring using rpm-ostree. According to the logs app, I am getting a "Failed to start ostree-boot-complete.service - OSTree Complete Boot" message.

Comment 1 Boricua 2022-08-13 15:09:18 UTC
I believe I fixed this issue. After a search, I found and applied the command "rpm-ostree cleanup -bprm". Then, I was able to apply the pending updates and removed the mailspring rpm. I think this bug report can be closed.


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