Bug 1473773

Summary:	[DOC] Incorrect live migration command in compute node upgrade section
Product:	Red Hat OpenStack	Reporter:	jliberma <jliberma>
Component:	documentation	Assignee:	Irina <igallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dan Macpherson <dmacpher>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0 (Mitaka)	CC:	aschultz, astillma, dbecker, dmacpher, igallagh, mariel, mbooth, mburns, morazi, mschuppe, stephenfin
Target Milestone:	zstream	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-04 08:41:33 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:

Description jliberma@redhat.com 2017-07-21 15:13:48 UTC

Description of problem:

Compute node upgrade suggestion uses "openstack server migrate" command but "nova migrate" command is required before the upgrade takes place due to target API version.

Version-Release number of selected component (if applicable):

Upgrading from OSP 9 to 10.

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/upgrading_red_hat_openstack_platform/#sect-Major-Upgrading_the_Overcloud-Compute

How reproducible:

This was reported by the customer but I did not have an environment to test.

According to the customer, these steps were required:

$ nova live-migration [instance-name] [target-hostname]
$ nova migration-list
$ nova resize-confirm [instance-name]

Comment 1 Martin Schuppert 2019-07-12 07:48:16 UTC

> Compute node upgrade suggestion uses "openstack server migrate" command but "nova migrate" command is required before the upgrade takes place due to target API version.

At the compute upgrade step [1] the control plane got already upgraded. Not sure what here is meant.

But the documentation suggests to use 'openstack server migrate' if a specific target compute should be used:

$ openstack server migrate [instance-id] --live [target-host]--wait

In case non shared storage is used this command stops as the default is:
  --shared-migration    Perform a shared live migration (default)

So I think in this case non shared storage was used and with openstack client --block-migration parameter needs to be added:
  --block-migration     Perform a block live migration

While the nova client when using API versions 2.25 and higher does auto detect:

$ nova help live-migration
usage: nova live-migration [--block-migrate] <server> [<host>]

Migrate running server to a new machine.

Positional arguments:
  <server>         Name or ID of server.
  <host>           Destination host name. If no host is specified, the
                   scheduler will choose one.

Optional arguments:
  --block-migrate  True in case of block_migration.
                   (Default=auto:live_migration) (Supported by API versions
                   '2.25' - '2.latest')

This also applies for later doc versions, e.g. [2]

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/upgrading_red_hat_openstack_platform/#sect-Major-Upgrading_the_Overcloud-Compute
[2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/upgrading_red_hat_openstack_platform/index#rebooting_compute_nodes

Comment 9 Irina 2020-08-04 08:41:33 UTC

Updated content available on the Customer Portal:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/upgrading_red_hat_openstack_platform/assembly-preparing_for_openstack-platform_upgrade#rebooting_compute_nodes