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. ** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => Medium ** Tags added: usability ** Summary changed: - Services can not be disabled + Confusing error message when trying to disable non-nova-compute service ** Also affects: nova/pike Importance: Undecided Status: New ** Also affects: nova/rocky Importance: Undecided Status: New ** Also affects: nova/queens Importance: Undecided Status: New ** Changed in: nova/queens Status: New => Triaged ** Changed in: nova/pike Status: New => Triaged ** Changed in: nova/pike Importance: Undecided => Medium ** Changed in: nova Importance: Medium => Low ** Changed in: nova Assignee: (unassigned) => Matt Riedemann (mriedem) ** Changed in: nova/rocky Importance: Undecided => Medium ** Changed in: nova/pike Importance: Medium => Low ** Changed in: nova/rocky Importance: Medium => Low ** Changed in: nova/queens Importance: Undecided => Low ** Changed in: nova/rocky Status: New => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1805164 Title: Confusing error message when trying to disable non-nova-compute service Status in OpenStack Compute (nova): Triaged Status in OpenStack Compute (nova) pike series: Triaged Status in OpenStack Compute (nova) queens series: Triaged Status in OpenStack Compute (nova) rocky series: Triaged Bug description: I'm trying to disable nova services, but the requests fail. python-nova-17.0.7-1.el7.noarch openstack-nova-api-17.0.7-1.el7.noarch openstack-nova-novncproxy-17.0.7-1.el7.noarch openstack-nova-placement-api-17.0.7-1.el7.noarch python2-novaclient-10.1.0-1.el7.noarch openstack-nova-conductor-17.0.7-1.el7.noarch openstack-nova-scheduler-17.0.7-1.el7.noarch openstack-nova-console-17.0.7-1.el7.noarch openstack-nova-common-17.0.7-1.el7.noarch How to reproduce: # openstack compute service set p024.domain.com nova-consoleauth --disable Failed to set service status to disabled Compute service nova-consoleauth of host p024.domain.com failed to set. Logs: Action: 'update', calling method: <function version_select at 0x7f49474a8938>, body: {"binary": "nova-consoleauth", "host": "p024.domain.com"} _process_stack /usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:604 HTTP exception thrown: Host 'p024.domain.com' is not mapped to any cell Returning 404 to user: Host 'p024.domain.com' is not mapped to any cell __call__ /usr/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:1064 XX.XX.XX.XX "PUT /v2.1/os-services/disable HTTP/1.1" status: 404 len: 511 time: 0.3039389 Why nova-consoleauth should be mapped to a cell? Is that a bug? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1805164/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
