Description of problem: There is a unit for it: # ls /usr/lib/systemd/system/openstack-swift-object-expirer.service /usr/lib/systemd/system/openstack-swift-object-expirer.service but the expirer doesn't run after packstack completes, Hower it can be started manually. Version-Release number of selected component (if applicable): openstack-packstack-2014.2-0.23.dev1468.gd049ea9.el7ost.noarch How reproducible: always Steps to Reproduce: 1. deploy 2. Check it is running [root@packstack ~(keystone_admin)]# systemctl |grep Expi Actual results: not running Expected results: openstack-swift-object-expirer.service loaded active running OpenStack Object Storage (swift) - Object Expirer Additional info:
I forgot to specify that it is disabled: # systemctl is-enabled openstack-swift-object-expirer.service disabled
Proposed https://review.openstack.org/223667 with the fix. Please note it requires https://review.openstack.org/211549
Moving it over to Ivan for packaging.
verified running and enabled: # uname -a Linux mabrams-svr021.scl.lab.tlv.redhat.com 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux # grep VERSION /etc/*release /etc/os-release:VERSION="7.2 (Maipo)" /etc/os-release:VERSION_ID="7.2" /etc/os-release:REDHAT_BUGZILLA_PRODUCT_VERSION=7.2 /etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION="7.2" # ls /etc/yum.repos.d/ redhat.repo rhel-optional.repo rhel-server.repo rhos-release-8.repo rhos-release.repo rhos-release-rhel-7.2.repo # systemctl is-enabled openstack-swift-object-expirer.service enabled # systemctl status openstack-swift-object-expirer.service ● openstack-swift-object-expirer.service - OpenStack Object Storage (swift) - Object Expirer Loaded: loaded (/usr/lib/systemd/system/openstack-swift-object-expirer.service; enabled; vendor preset: disabled) Active: active (running) since ג' 2016-01-26 09:47:11 IST; 4h 0min ago Main PID: 7091 (swift-object-ex) CGroup: /system.slice/openstack-swift-object-expirer.service └─7091 /usr/bin/python2 /usr/bin/swift-object-expirer /etc/swift/object-expirer.conf ינו 26 13:34:54 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass beginning; 0 possible container...s ינו 26 13:34:54 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass completed in 0s; 0 objects expired ינו 26 13:39:01 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass beginning; 0 possible container...s ינו 26 13:39:01 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass completed in 0s; 0 objects expired ינו 26 13:40:55 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass beginning; 0 possible container...s ינו 26 13:40:55 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass completed in 0s; 0 objects expired ינו 26 13:42:09 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass beginning; 0 possible container...s ינו 26 13:42:09 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass completed in 0s; 0 objects expired ינו 26 13:45:50 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass beginning; 0 possible container...s ינו 26 13:45:50 mabrams-svr021.scl.lab.tlv.redhat.com object-expirer[7091]: Pass completed in 0s; 0 objects expired Hint: Some lines were ellipsized, use -l to show in full. # ps -ef | grep Expi root 19132 27543 0 13:48 pts/2 00:00:00 grep --color=auto Expi #
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/RHEA-2016-0603.html