Errors "Invalid response returned from server" and "The management service may be unavailable" Encountered During Object Storage Migration (KBA10740)

Issue

Delphix does not currently recommend leveraging In-Place Object Storage Migration until 19.0.0.0 or later, due to the issue outlined in Technical Bulletin TB113

During the process of In-Place Object Storage Migration (currently a CLI-only operation), the following error may be encountered:

delphixEngine storage migrate start *> commit
Invalid response returned from server. The management service may be unavailable, please wait and try again. If the problem persists, please contact Delphix support.

The Management service will also restart, which may disrupt jobs in progress at the time of the event.

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies

Date	Release
Dec 20, 2023 | Jan 10, 2024	18.0.0.0 | 18.0.0.1
Nov 21, 2023	17.0.0.0
Oct 18, 2023	16.0.0.0
Sep 21, 2023	15.0.0.0

Resolution

This behavior is known to occur when an S3 object configuration is committed in the migrate process, when the region parameter is left unset. Although this parameter may not be applicable to "on-premises" S3 object storage, the Engine CLI does not properly handle this condition.

The parameters of the CLI transaction can be reviewed prior to commit, and if the region parameter is unset or not applicable, it can be set to a dummy value (us-west-2, for example).

delphixEngine storage migrate start *> ls
Properties
    type: S3ObjectStore (*)
    accessCredentials:
        type: S3ObjectStoreAccessKey (*)
        accessId: exampleidforKBA (*)
        accessKey: ******** (*)
    bucket: example-computer-field (*)
    cacheDevices: Disk0:3 (*)
    configured: false
    endpoint: http://exampleserver.delphix.com:9000 (*)
    region: (unset) <<<<<<<<<<<
    size: 8GB (*)
delphixEngine storage migrate start *> set region=us-west-2
delphixEngine storage migrate start *> commit

This issue is targeted to be resolved in 20.0.0.0 release

This issue is tracked via DLPX-89610