Bug 1461096

Summary: Remove packages for monitoring after upgrading to Satellite 5.8 from old version
Product: Red Hat Satellite 5 Reporter: Michael Mráka <mmraka>
Component: InstallerAssignee: Gennadii Altukhov <galtukho>
Status: CLOSED ERRATA QA Contact: Ales Dujicek <adujicek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 580CC: adujicek, dyordano, galtukho, mmraka, pstudeni, tlestach, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhn-upgrade-5.8.0.27-1-sat Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1417237 Environment:
Last Closed: 2017-10-19 11:59:23 UTC Type: Bug
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: 1450111    
Attachments:
Description Flags
patch provides tool to remove monitoring packages none

Comment 1 Gennadii Altukhov 2017-08-01 15:43:57 UTC
Created attachment 1307718 [details]
patch provides tool to remove monitoring packages

Comment 2 Gennadii Altukhov 2017-08-01 15:45:03 UTC
Added a tool to remove monitoring packages and updated upgrade documentation.

Comment 3 Tomas Lestach 2017-08-02 08:19:22 UTC
Do we really want to introduce a new log file /var/log/rhn/remove-monitoring-pkgs.log just for this script purpose? Cannot we re-use an existing one?

Comment 4 Gennadii Altukhov 2017-08-08 14:15:00 UTC
Tomas, I thought about re-using some of the existing log, but in this case 1) the script should lock the file, to be sure nothing else use it 2) anyway it's possible to mess the log messages which is not really good.

Comment 9 Tomas Lestach 2017-08-14 14:54:22 UTC
Grant had a good point. Please make sure, the new log file gets automatically picked up by sosreport/spacewalk-debug. Thank you.

Comment 14 errata-xmlrpc 2017-10-19 11:59:23 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, 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-2017:2914