e7b84daa87
Change If1e03c9343b8cc9c34bd51c2b4d25acdb21131ff in the API in Pike makes the os-services API look up services records via the host mapping in the API datadabase to determine which cell the service lives in. The host mappings only exist for nova-compute services, which means you can only enable/disable/force-down nova-compute services now, which is realistically the only service that ever made sense for those actions. That change broke some functional tests in novaclient though which loop through all services and disables them or forces them down. This change fixes those tests by only attempting the action on nova-compute services. This change also deprecates the binary argument to the service enable/disable/force-down commands since the only value that ever really worked or does anything is nova-compute, so a future version of the CLI should just hard-code that value. Change-Id: Idd0d2be960ca0ed59097c10c931da47a1a3e66fb Closes-Bug: #1700359
11 lines
505 B
YAML
11 lines
505 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The ``binary`` argument to the ``nova service-enable``,
|
|
``nova service-disable``, and ``nova service-force-down`` commands has been
|
|
deprecated. The only binary that it makes sense to use is ``nova-compute``
|
|
since disabling a service like ``nova-scheduler`` or ``nova-conductor``
|
|
does not actually do anything, and starting in the 16.0.0 Pike release the
|
|
compute API will not be able to look up services other than
|
|
``nova-compute`` for these operations.
|