Bug 1399564

Summary: openstack-swift-object-expirer service not running on TripleO deployment
Product: Red Hat OpenStack Reporter: Christian Schwede (cschwede) <cschwede>
Component: puppet-tripleoAssignee: Christian Schwede (cschwede) <cschwede>
Status: CLOSED ERRATA QA Contact: Mike Abrams <mabrams>
Severity: high Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: cschwede, egafford, jjoyce, jschluet, mabrams, pgrist, sclewis, scohen, slinaber, tvignaud
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-5.5.0-13.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-28 14:44:12 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:

Description Christian Schwede (cschwede) 2016-11-29 10:15:46 UTC 
Description of problem:

openstack-swift-object-expirer service not running on TripleO deployment

Version-Release number of selected component (if applicable):

Newton

How reproducible:

Always

Steps to Reproduce:
1. Deploy TripleO

Actual results:

openstack-swift-object-expirer service not running on controller nodes

Expected results:

openstack-swift-object-expirer service running on controller nodes
Comment 3 Christian Schwede (cschwede) 2017-02-17 08:22:24 UTC 
Patch merged upstream and included in downstream build. Changing status to MODIFIED.
Comment 4 Jon Schlueter 2017-02-23 16:43:28 UTC 
(In reply to Christian Schwede (cschwede) from comment #3)
> Patch merged upstream and included in downstream build. Changing status to
> MODIFIED.

The above mentioned build was for OSP 11 and not 10.  Moving back to POST
Comment 16 errata-xmlrpc 2017-06-28 14:44:12 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:1585