Assigning to DFG:Storage for triage, maybe the restart should be handled by puppet-swift
I just installed a fresh OSP12 environment, but can't reproduce this - Swift is logging correctly to /var/log/swift/swift.log in my environment. Shinobu, can you share more information with me please? How did you install it, which zstream release etc.? That would be helpful to reproduce this issue and find the root cause. Thx!
Hello Christian, I tried to install undercloud on my KVM env. And the issue can be reproduced. The using RHOSP12 is current latest release via Red Hat Customer Portal. I did steps written in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/director_installation_and_usage/
Upstream backport merged: https://review.openstack.org/#/c/587696/
Verified on: instack-undercloud-8.4.6-2.el7ost.noarch [stack@undercloud-0 ~]$ sudo cat /etc/rsyslog.d/openstack-swift.conf # LOCAL2 is what Swift gets in RHOS and RDO if installed with Packstack (also, # in docs). The breakout action prevents logging into /var/log/messages, # bz#997983. local2.* /var/log/swift/swift.log & stop This is fixed ^ as was before. But now when I tail or tailf swift's log I see log progressing. No Swift restart was needed, OK to verify. [stack@undercloud-0 ~]$ sudo tail /var/log/swift/swift.log Oct 31 07:50:14 undercloud-0 account-server: 192.168.24.1 - - [31/Oct/2018:11:50:14 +0000] "HEAD /1/97/.expiring_objects" 204 - "HEAD http://localhost/v1/.expiring_objects?format=json" "tx0970fad9f0684651ab08d-005bd996f6" "proxy-server 19877" 0.0023 "-" 21630 - Oct 31 07:50:14 undercloud-0 object-expirer: Pass beginning; 0 possible containers; 0 possible objects (txn: tx0970fad9f0684651ab08d-005bd996f6) Oct 31 07:50:14 undercloud-0 account-server: 192.168.24.1 - - [31/Oct/2018:11:50:14 +0000] "GET /1/97/.expiring_objects" 200 2 "GET http://localhost/v1/.expiring_objects?marker=&prefix=&end_marker=&format=json" "txc7f2745dbd2c4dbbb3002-005bd996f6" "proxy-server 19877" 0.0020 "-" 21630 - Oct 31 07:50:14 undercloud-0 object-expirer: Pass completed in 0s; 0 objects expired (txn: txc7f2745dbd2c4dbbb3002-005bd996f6)
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:3587