Bug 1316555

Summary: Mention in doc that satellite services should be stopped before running yum update
Product: Red Hat Satellite 5 Reporter: Lukáš Hellebrandt <lhellebr>
Component: UpgradesAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED ERRATA QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-28 11:16:10 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:
Attachments:
Description Flags
catalina.out none

Description Lukáš Hellebrandt 2016-03-10 13:19:00 UTC
Created attachment 1134892 [details]
catalina.out

Description of problem:
When running yum update with satellite services running, tomcat complains that we are changing things while it is running. (Traceback attached but probably not important.)
This should be mentioned in rhn-upgrade package's upgrade guide, perhaps in part 2) of /etc/sysconfig/rhn/satellite-upgrade/doc/preparations.txt

Version-Release number of selected component (if applicable):
Tested on Sat 5.4.1

How reproducible:
Deterministic

Steps to Reproduce:
1. Have a not-up-to-date satellite, running.
2. yum update
3. cat /var/log/tomcat6/catalina.out

Actual results:
Tracebacks in catalina.out

Expected results:
No tracebacks

Comment 1 Lukáš Hellebrandt 2016-03-10 13:24:17 UTC
To clarify: expected result is "No tracebacks because there was an instruction to shut down satellite services in the upgrade docs"

Comment 4 Lukáš Hellebrandt 2016-03-29 09:42:28 UTC
Verified with rhn-upgrade-5.7.0.30-1 , the correct way is now described in preparations.txt.

Comment 6 errata-xmlrpc 2016-04-28 11:16:10 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://rhn.redhat.com/errata/RHBA-2016-0698.html