# BFV Instance Fails to Migrate: "Driver initialize connection failed (error: PureHTTPError status code 400)

## Problem

* A boot-from-volume (BFV) instance is failing to migrate with the following error shown in the */var/log/pf9/ostackhost.log* file on the respective hypervisor host.

{% tabs %}
{% tab title="None" %}

```none
ERROR cinder.api.middleware.fault [...] Caught error: [class 'oslo_messaging.rpc.client.RemoteError'] Remote error: VolumeBackendAPIException Bad or unexpected response from the storage volume backend API: Driver initialize connection failed (error: PureHTTPError status code 400 returned by REST version 1.5 at 10.248.8.123: BAD REQUEST
```

{% endtab %}
{% endtabs %}

* A similar error is observed on the Block Storage host in the */var/log/pf9/cindervolume-base.log* file.

{% tabs %}
{% tab title="None" %}

```none
[{"msg": "Volume does not exist.", "ctx": "volume-58afa6e7-c8c4-473e-a95c-d948b0a4584e-cinder"}]).: PureHTTPError: PureHTTPError status code 400 returned by REST version 1.5 at 10.248.8.123: BAD REQUEST
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Cinder
* Pure Storage Backend

## Cause

In Pure Storage, volumes that are/were managed by OpenStack Block Storage ( *Cinder*) were moved to a *Volume Group* – thus, affecting the filename schema/path and causing the volumes to be no longer recognized.

## Resolution

The volumes can be fixed by moving them back out of the *Volume Group* to the root container of the array. This reverts the name to the *Cinder* recognized name.