Description of problem: Users may shut down clients, while in the middle of an upgrade, renderung the client unusable afterwads. Version-Release number of selected component (if applicable): Spacewalk 2.6 How reproducible: Always Steps to Reproduce: 1. Install Spacewalk client, initiate an upgrade from server 2. Call shutdown or halt while the upgrade is working 3. Watch the client shut down Actual results: Client shuts down without any warning or notice Expected results: Client shall inform the user about the ongoing upgrade and it will shut down after finishing it. Additional info: Under circumstances this may lead to non booting systems later on, because missing files from grub. A humbled grub configuration, missing kernel or wrong kernel. System booting, but unable to start X11, or starting X11, but no displaymanager (empty X11 screen with mouse. No menue, maybe even no background). Applications not starting, because of missing libraries (including applications necessary for spacewalk -- absolute fatal: yum exceptions or rpm crashing).
This is more RFE than a real bug. It should be better handled on a system / yum / dnf level because spacewalk client just runs dnf (or yum) to do the upgrade.
Spacewalk project as an upstream for Red Hat Satellite 5 product is going to be End Of Life on May 31 2020. Spacewalk 2.10 has been released as the last release of this project. https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes210 Any new feature will not be included therefore closing remaining RFEs to set expectations properly.