As Takashi noted, disabling/enabling/forcing down/up services is only for compute services. There is no functional point to disabling conductor/scheduler/consoleauth. This was noted in the Pike release notes:
https://docs.openstack.org/releasenotes/nova/pike.html#relnotes-16-0-0-stable-pike-other-notes
The thing I think Takashi notes is the confusing error message:
"HTTP exception thrown: Host 'p024.domain.com' is not mapped to any cell"
We could check the binary in that case and if it's not 'compute' then we can provide a more useful error message.
As Takashi noted, disabling/ enabling/ forcing down/up services is only for compute services. There is no functional point to disabling conductor/ scheduler/ consoleauth. This was noted in the Pike release notes:
https:/ /docs.openstack .org/releasenot es/nova/ pike.html# relnotes- 16-0-0- stable- pike-other- notes
The thing I think Takashi notes is the confusing error message:
"HTTP exception thrown: Host 'p024.domain.com' is not mapped to any cell"
We could check the binary in that case and if it's not 'compute' then we can provide a more useful error message.