Bug 1638311 - [OSP14] After a 13->14 UC upgrade some swift services are still running outside of containers
Summary: [OSP14] After a 13->14 UC upgrade some swift services are still running outsi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Christian Schwede (cschwede)
QA Contact: Mike Abrams
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-11 10:24 UTC by Michele Baldessari
Modified: 2019-01-11 11:54 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.1-0.20181013060865.ffbe879.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:53:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1798366 0 None None None 2018-10-17 12:19:16 UTC
OpenStack gerrit 611571 0 None MERGED Disable non-containerized Swift services 2020-06-01 02:53:49 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:54:00 UTC

Description Michele Baldessari 2018-10-11 10:24:50 UTC 
Description of problem:
1. Upgrade UC from 13 to 14
2. Observe that we still have a couple of swift baremetal services:
swift       1446  0.0  0.1 287108 31236 ?        Ss   05:42   0:00 /usr/bin/python2 /usr/bin/swift-container-sync /etc/swift/container-server.conf
swift       1451  0.0  0.1 277928 29188 ?        Ss   05:42   0:00 /usr/bin/python2 /usr/bin/swift-object-reconstructor /etc/swift/object-server.conf

Most swift services are correctly migrated to containers. So these either need to be migrated to containers or they need to be removed.
Comment 3 Christian Schwede (cschwede) 2018-10-18 10:34:10 UTC 
Upstream patch merged -> POST.
Comment 4 Jiri Stransky 2018-10-18 11:08:12 UTC 
(Switching the patch link to stable/rocky backport.)
Comment 22 errata-xmlrpc 2019-01-11 11:53:52 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/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.