Comment 3 for bug 1273151

Current behavior is expected.

'disabled' flag is only a tag in DB for services. The tricky part is, the service itself doesn't actually do anything when its status is being changed (via admin API). Only scheduler honors 'disabled' flag of OTHER services (in Cinder context, cinder-volume service). I think the purpose of introducing 'disabled' flag was to allow admin to easily put a service (cinder-volume, and similarly nova-compute) into/out of available resource pool. Scheduler will not consider disabled service when making resource placement decision.

It's funny when you try to disable scheduler itself. It updates the flag in DB, but no one actually looks at the flag for scheduler, which I think is fine. To me, there's not much value to 'disable' a schedule, it may help a bit when you are debugging multi-scheduler environment but to make it work like that way you want it, there is quite a bit of work to do (e.g. have c-api to notify a service that it's been disabled and to make service react such notification).

For the reason above, I'd suggest we invalid this bug or make it to wishlist.