Bug 1530694

Summary: Upgrade of Satellite to 6.2.11 error on removal of qpid dat2 directory
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.11CC: ajoseph, bbuckingham, bkearney, brubisch, cdonnell, chrobert, egolov, ehelms, fgarciad, gkonda, hmore, inecas, jalviso, jyejare, ktordeur, mbacovsk, michiel.smit, mmccune, mmithaiw, mverma, pdwyer, peter.vreman, pgervase, pmoravec, pmutha, sghai, smane, swadeley, vijsingh, xdmoon
Target Milestone: UnspecifiedKeywords: ManyUsersImpacted, PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Upgrading from 6.2.10 to 6.2.11 without correctly stopping services can cause the upgrade to fail on removing qpid data. This case is now handled properly.
Story Points: ---
Clone Of: 1482539 Environment:
Last Closed: 2018-02-21 12:41:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Jitendra Yejare 2018-01-10 15:20:20 UTC
Hi Pavel,

May I have the repro steps to verify this bug ?

Comment 3 Jitendra Yejare 2018-02-01 16:37:32 UTC
Verified!

@ Satellite 6.3 snap 34

Steps:

Without stopping services:

1. installed Satellite 6.2
2. yum update os and sat packages to 6.3
3. satellite-installer --scenario satellite --upgrade

With stopping services:

1. installed Satellite 6.2
2. yum update(os packages)
3. stop services
4. yum update(satellite packages)
5. satellite-installer --scenario satellite --upgrade

Observation:

1. Upgrade is successful in both the cases
2. No dat2 directory removal related failure
3. qpid queues are preserved during and post upgrade

Comment 4 Jitendra Yejare 2018-02-01 16:38:51 UTC
The bug is verified with the help of steps from https://bugzilla.redhat.com/show_bug.cgi?id=1482539#c31

Comment 7 errata-xmlrpc 2018-02-21 12:41:31 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-2018:0337