Looking at logstash, this started happening really around Nov 4:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22AllocationUpdateFailed%3A%20Failed%20to%20update%20allocations%20for%20consumer%5C%22%20AND%20message%3A%5C%22Error%3A%20another%20process%20changed%20the%20consumer%5C%22%20AND%20message%3A%5C%22after%20the%20report%20client%20read%20the%20consumer%20state%20during%20the%20claim%5C%22%20AND%20(tags%3A%5C%22console%5C%22%20OR%20tags%3A%5C%22screen-n-sch.txt%5C%22)&from=10d
Looking at logstash, this started happening really around Nov 4:
http:// logstash. openstack. org/#dashboard/ file/logstash. json?query= message% 3A%5C%22Allocat ionUpdateFailed %3A%20Failed% 20to%20update% 20allocations% 20for%20consume r%5C%22% 20AND%20message %3A%5C% 22Error% 3A%20another% 20process% 20changed% 20the%20consume r%5C%22% 20AND%20message %3A%5C% 22after% 20the%20report% 20client% 20read% 20the%20consume r%20state% 20during% 20the%20claim% 5C%22%20AND% 20(tags% 3A%5C%22console %5C%22% 20OR%20tags% 3A%5C%22screen- n-sch.txt% 5C%22)& from=10d