Bug 1291272 - [RFE] Yum should notify if a reboot is needed after updating any such packages
[RFE] Yum should notify if a reboot is needed after updating any such packages
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum (Show other bugs)
6.7
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Valentina Mukhamedzhanova
BaseOS QE Security Team
: FutureFeature
Depends On:
Blocks: 1269194
  Show dependency treegraph
 
Reported: 2015-12-14 08:33 EST by Adi Akbar
Modified: 2016-07-25 10:15 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-25 10:15:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adi Akbar 2015-12-14 08:33:22 EST
FEATURE REQUEST
---------------

1. Proposed title of this feature request  

-- Yum should tag something as 'action required' once after upgrading any critical packages, if the reboot or service restart is required.
      
2. Who is the customer behind the request?  

Account: NCG BANCO SA, acc # 5266593
  
TAM customer: no 
SRM customer: no
Strategic: no  
      
3. What is the nature and description of the request?  

-- Yum should inform user, if a reboot or restart of a service is required after software updates are performed. 
      
4. Why does the customer need this? (List the business requirements here)  

-- Customer wants to know if a reboot or restart of a service is required after software updates are performed. They do not want to reboot their system each time they run updates. Having a flag that warns them when to reboot/restart (as SLES or Debian) will be of great help.
      
5. How would the customer like to achieve this? (List the functional requirements here)  

-- Customer wants the feature with yum. They are looking for something similar to what Suse does when you update with zypper.
After an upgrade is made it asks you to review with command "zypper ps" which processes need to be restarted to complete upgrades.

As someone else pointed out at the discussion thread Debian also let's you know this on file /var/run/reboot-required.pkgs.

They have found this looking for reboot-required.pkgs which I think sums up the idea very well: http://askubuntu.com/questions/28530/how-can-i-tell-what-package-requires-a-reboot-of-my-system
      
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

-- With the help of running a # yum update
      
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  

-- No
      
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  

-- Customer would like to achieve this with both RHEL 6 and 7.
      
9. Is the sales team involved in this request and do they have any additional input?  

-- No
      
10. List any affected packages or components.  

-- Yum
      
11. Would the customer be able to assist in testing this functionality if implemented?  

-- Yes

-----------------------------------------------------------------------------------------

Seeking collaboration: If this functionality is made available, this would help a lot of customers. We have noticed a lot of concerns over this in the past few months.

https://access.redhat.com/discussions/682263

------------------------------------------------------------------------------------------
Comment 3 Valentina Mukhamedzhanova 2016-07-25 10:15:19 EDT
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.

This request is being tracked in Red Hat Enterprise Linux version 7 in bug 1192946 and bug 1335587.

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