Bug 2056786

Summary: [RFE] Cockpit : Add option to Reboot the system after successful package update
Product: Red Hat Enterprise Linux 9 Reporter: Ravindra Patil <ravpatil>
Component: cockpitAssignee: Martin Pitt <mpitt>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: unspecified Docs Contact: Laura Onduskova <londusko>
Priority: unspecified    
Version: 9.0CC: lmanasko, mpitt, sbarcomb
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 9.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-273-1.el9 Doc Type: Enhancement
Doc Text:
.Update progress page in the web console now supports an automatic restart option The update progress page now has a *Reboot after completion* switch. This reboots the system automatically after installing the updates.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 11:16:26 UTC Type: Feature Request
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: 2038517    
Attachments:
Description Flags
expected reboot/restart dialog after installing updates none

Description Ravindra Patil 2022-02-22 04:18:12 UTC 
Description of problem:

Please add option either a button or checkbox to choose to reboot the system after successful updates of the packages in cockpit. 

Currently, we need to update the packages and then reboot the system manually when the the package updates are complete. 

As part of package updates using cockipt, requesting for two things :

- Check box or button to select a reboot on a successful install/update. 
- Dropdown for the wait time and a message to sent to the users during reboot.

Version-Release number of selected component (if applicable):
260-1.el9.x86_64.rpm

How reproducible:
Update the packages using cockpit and then wait for them to complete and then reboot the system manually. 

Steps to Reproduce:
1. Select packages to update using cockpit
2. Update the selected packages
3. Wait for the updates and manually reboot the system. 

Actual results:
Need to reboot after package update manually. 

Expected results:
Option to set system to reboot after package update. 

Additional info:
This feature would really help to save customer's time and efforts as they need not to watch for package updates. 

Instead cockpit would make sure to reboot the system after successful updates of the package.
Comment 2 Martin Pitt 2022-02-22 05:35:59 UTC 
Created attachment 1862504 [details]
expected reboot/restart dialog after installing updates

> 3. Wait for the updates and manually reboot the system. 

I suppose with "manual" you mean "Click the reboot button" after installing updates is complete? Or that you somehow don't get this screen, and you mean "go to a terminal and type 'reboot'"? It is expected to look like the attached screenshot.

I.e. you want us to add an option to the "update in progress" page (with the scrollbar and update log) to reboot after success?

Note that in a lot of cases you don't actually need a reboot. Tracer will check if it is enough to restart running services, and Cockpit will offer to do that. However, this can only be determined after installing updates is complete. In my case it involved a kernel update, and as RHEL 9.0 does not yet have kpatches, it has to reboot. But with released RHELs and kpatch, there should actually be a lot less need to do reboots.
Comment 8 Martin Pitt 2022-06-24 19:46:59 UTC 
I sent https://github.com/cockpit-project/cockpit/pull/17500 to add this. It still needs some design tweaking, though. I posted a screenshot, if you are interested.
Comment 14 errata-xmlrpc 2022-11-15 11:16:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (cockpit bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8314