MountVolume.SetUp error for Windows migrations

When migrating a Windows workload, you might see the following error:

MountVolume.SetUp failed for volume "VOLUME_NAME" :
  mount command failed, status: Failure,
  reason: Error: failed locking disk VOLUME_NAME
  to pod POD_NAME: already in use by pod POD_NAME

If this error appears for more than 15 minutes with no progress:

Delete the migration.
Recreate the migration and try it again.

If the issue persists, see Getting support for information about contacting Support.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2024-04-24 UTC.