The issue stems from RHOSO18's openstacksdk package missing a critical `force` parameter patch that was added in newer versions. When OS-Migrate attempts to create volume snapshots during workload migration from RHOSP16.2, the operation fails because the older SDK version doesn't support the required `force` parameter for attached volumes. This blocks boot-from-volume migrations where data_copy=true is necessary. The solution requires either backporting the missing patch to RHOSO18's openstacksdk package or implementing version detection logic in OS-Migrate to handle different SDK versions gracefully.

See here - https://issues.redhat.com/browse/OSPRH-17963