yahoo-eng-team team mailing list archive

[Takashi NATSUME <natsume.takashi@xxxxxxxxxxxxx>]

Public bug reported:

In "Force Migration Complete Action" API(*1), the 'force_complete' parameter in the request is defined as 'string'.
This parameter is always 'null'(*2).
In the other APIs, it is defined as 'none' (e.g. "Start Server" API (*3)) in that case.
So It should be 'none' as well in "Force Migration Complete Action" API.

*1: https://developer.openstack.org/api-ref/compute/#force-migration-complete-action-force-complete-action
*2: https://github.com/openstack/nova/blob/a40c00957ef4552681c172913bae1135a1614bbc/nova/api/openstack/compute/schemas/server_migrations.py#L21
*3: https://developer.openstack.org/api-ref/compute/#start-server-os-start-action

** Affects: nova
     Importance: Undecided
     Assignee: Takashi NATSUME (natsume-takashi)
         Status: In Progress


** Tags: api-ref

** Changed in: nova
       Status: New => In Progress

-- 
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/1744688

Title:
  api-ref: wrong parameter type in server-migrations.inc

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  In "Force Migration Complete Action" API(*1), the 'force_complete' parameter in the request is defined as 'string'.
  This parameter is always 'null'(*2).
  In the other APIs, it is defined as 'none' (e.g. "Start Server" API (*3)) in that case.
  So It should be 'none' as well in "Force Migration Complete Action" API.

  *1: https://developer.openstack.org/api-ref/compute/#force-migration-complete-action-force-complete-action
  *2: https://github.com/openstack/nova/blob/a40c00957ef4552681c172913bae1135a1614bbc/nova/api/openstack/compute/schemas/server_migrations.py#L21
  *3: https://developer.openstack.org/api-ref/compute/#start-server-os-start-action

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1744688/+subscriptions