Bug 1530694 - Upgrade of Satellite to 6.2.11 error on removal of qpid dat2 directory
Summary: Upgrade of Satellite to 6.2.11 error on removal of qpid dat2 directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.11
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-03 16:13 UTC by Satellite Program
Modified: 2021-09-09 12:59 UTC (History)
30 users (show)

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.
Clone Of: 1482539
Environment:
Last Closed: 2018-02-21 12:41:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3157651 0 None None None 2018-01-03 16:14:13 UTC
Red Hat Product Errata RHBA-2018:0337 0 normal SHIPPED_LIVE Red Hat Satellite 6.3 Base Libraries 2018-02-21 19:26:10 UTC

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
Note You need to log in before you can comment on or make changes to this bug.