logstack says this has showed up Nov 23 UTC:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiTG9jayB3YWl0IHRpbWVvdXQgZXhjZWVkZWQ7IHRyeSByZXN0YXJ0aW5nIHRyYW5zYWN0aW9uXCIgQU5EIG1lc3NhZ2U6XCJkZWxldGVfcG9ydFwiIEFORCBmaWxlbmFtZTpcImxvZ3Mvc2NyZWVuLXEtc3ZjLnR4dFwiIiwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJvZmZzZXQiOjAsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzg1MTgzOTE0NDk2fQ==
I wonder if this has been introduced by this one:
https://review.openstack.org/#/c/54918
which incidentally merged right about when the error started showing up.
logstack says this has showed up Nov 23 UTC:
http:// logstash. openstack. org/#eyJmaWVsZH MiOltdLCJzZWFyY 2giOiJtZXNzYWdl OlwiTG9jayB3YWl 0IHRpbWVvdXQgZX hjZWVkZWQ7IHRye SByZXN0YXJ0aW5n IHRyYW5zYWN0aW9 uXCIgQU5EIG1lc3 NhZ2U6XCJkZWxld GVfcG9ydFwiIEFO RCBmaWxlbmFtZTp cImxvZ3Mvc2NyZW VuLXEtc3ZjLnR4d FwiIiwidGltZWZy YW1lIjoiNjA0ODA wIiwiZ3JhcGhtb2 RlIjoiY291bnQiL CJvZmZzZXQiOjAs InRpbWUiOnsidXN lcl9pbnRlcnZhbC I6MH0sInN0YW1wI joxMzg1MTgzOTE0 NDk2fQ= =
I wonder if this has been introduced by this one:
https:/ /review. openstack. org/#/c/ 54918
which incidentally merged right about when the error started showing up.