Bug 1598908 - unable to live migrate instances when specifying nova api version 2.30
Summary: unable to live migrate instances when specifying nova api version 2.30
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-openstackclient
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z10
: 10.0 (Newton)
Assignee: Julie Pichon
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks: 1633723 1633726
TreeView+ depends on / blocked
 
Reported: 2018-07-06 20:13 UTC by nalmond
Modified: 2022-03-13 15:12 UTC (History)
5 users (show)

Fixed In Version: python-openstackclient-3.2.1-7.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1633723 (view as bug list)
Environment:
Last Closed: 2019-01-16 17:09:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 582334 0 None None None 2018-07-12 18:38:18 UTC
Red Hat Product Errata RHBA-2019:0075 0 None None None 2019-01-16 17:09:28 UTC
Storyboard 2002963 0 None None None 2018-07-12 18:23:37 UTC

Description nalmond 2018-07-06 20:13:17 UTC 
Description of problem:
When forcing openstack client to use nova api version 2.30, the command fails with an unrecognized argument error.

How reproducible:
Every time

Steps to Reproduce:
1. Create an instance
2. Attempt to migrate the instance with:
$ openstack server migrate --os-compute-api-version 2.30 --live <compute> <instance-id>
3.

Actual results:
Command fails with:
live_migrate() got an unexpected keyword argument 'disk_over_commit'

Expected results:
Migration completes successfully

Additional info:
novaclient works as expected:
$ nova --os-compute-api-version 2.30 live-migration <instance> <compute>

This looks to be related to the removal of disk_over_commit in version 2.25 https://developer.openstack.org/api-ref/compute/#live-migrate-server-os-migratelive-action
Comment 18 errata-xmlrpc 2019-01-16 17:09:07 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0075
Note You need to log in before you can comment on or make changes to this bug.