Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1598908

Summary: unable to live migrate instances when specifying nova api version 2.30
Product: Red Hat OpenStack Reporter: nalmond
Component: python-openstackclientAssignee: Julie Pichon <jpichon>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: apevec, jpichon, lhh, lyarwood, srevivo
Target Milestone: z10Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-openstackclient-3.2.1-7.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1633723 (view as bug list) Environment:
Last Closed: 2019-01-16 17:09:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1633723, 1633726    

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