Swift object-expirer uses wrong memcached IP on separate storage nodes

[Christian Schwede]

The Swift object-expirer uses the wrong memcached IP on separate storage nodes.

It is set to the default 127.0.0.1:11211 if the proxy service config is not applied on the same node, eg. when using seperate storage nodes. It also looks messages like this:

object-expirer: STDERR: ERROR:root:Error connecting to memcached: 127.0.0.1:11211: [Errno 111] ECONNREFUSED

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/744015

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/744015
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=e7cb55d97b41c35800e08257a826164ca5a1c7de
Submitter: Zuul
Branch: master

commit e7cb55d97b41c35800e08257a826164ca5a1c7de
Author: Christian Schwede <email address hidden>
Date: Thu Jul 30 18:33:02 2020 +0200

    Use correct memcached IPs for Swift object-expirer

    The memcached IP is not properly set in case of separate storage nodes.
    Until now, these were only set if the Swift proxy node was also
    configured on the same node; however, this is not the case with separate
    storage nodes. The service would still run, but was not able to use any
    cache and logging errors therefore.

    Closes-Bug: 1889663
    Change-Id: I70ac9fcd3f74975c96c715ecbc818e6606ff4517