Comment 5 for bug 1644751

FYIW we just experienced that symptom on two out of three cinder-scheduler instances that came up in a brand new deployment (running latest Queens Cinder version 12.0.4 as deployed by OSA 17.0.8).

In addition to the symptomatic error msg ("WARNING oslo_messaging.server [req-5ea6475e-e930-4ff0-9d17-20189aa85ba1 - - - - -] Possible hang: wait is waiting for stop to complete") cinder-scheduler was gobbling up 100% CPU. A bounce of both hung processes cured the issue.