| 2017-06-16 17:34:08 |
Alex Schultz |
description |
Upstream is adding management of swift-object-reconstructor[0] into the swift::storage::object class but noop is reporting a duplicate service declaration due to a workaround[1] in place to disable the service on trusty.
Since trusty hasn't been supported on master for a long time, we should probably just pull the service disabling for trusty.
[0] https://review.openstack.org/#/c/445998/
[1] https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack_tasks/manifests/swift/proxy_storage.pp#L179-L194 |
Upstream is adding management of swift-object-reconstructor[0] into the swift::storage::object class but noop is reporting a duplicate service declaration due to a workaround[1] in place to disable the service on xenial.
[0] https://review.openstack.org/#/c/445998/
[1] https://github.com/openstack/fuel-library/blob/master/deployment/puppet/openstack_tasks/manifests/swift/proxy_storage.pp#L179-L194 |
|
