Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.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.
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.
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.
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