From 765cc945d67deaf029e700885aa41ed2c72982eb Mon Sep 17 00:00:00 2001 From: Clay Gerrard Date: Thu, 1 Dec 2016 07:30:40 -0800 Subject: [PATCH] Fixups for ghost listing fix I think the probetest can be a little more pathological and I'm worried about logging the response of each individual request at error when we currently only log the entire failure at debug. I have lots of async pendings sometimes. Related-Change: Ic5d55ff368cec62ab2eb9fd883801ba4ab043dd4 Change-Id: I1c070b2b07d31552f36b647731b0b3ebed31871f --- swift/obj/updater.py | 2 +- test/probe/test_object_async_update.py | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/swift/obj/updater.py b/swift/obj/updater.py index a8504dd576..bcb73dd3af 100644 --- a/swift/obj/updater.py +++ b/swift/obj/updater.py @@ -270,7 +270,7 @@ class ObjectUpdater(Daemon): resp.read() success = is_success(resp.status) if not success: - self.logger.error( + self.logger.debug( _('Error code %(status)d is returned from remote ' 'server %(ip)s: %(port)s / %(device)s'), {'status': resp.status, 'ip': node['ip'], diff --git a/test/probe/test_object_async_update.py b/test/probe/test_object_async_update.py index 42a11d90b3..cc924c950d 100644 --- a/test/probe/test_object_async_update.py +++ b/test/probe/test_object_async_update.py @@ -109,6 +109,9 @@ class TestObjectAsyncUpdate(ReplProbeTest): self.assertFalse(direct_client.direct_get_container( cnode, cpart, self.account, container)[1]) + # since the container is empty - we can delete it! + client.delete_container(self.url, self.token, container) + # Re-run the object-updaters and now container replicas in primary # container servers should get updated Manager(['object-updater']).once()