> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/bfv-instance-fails-to-migrate-driver-initialize-connection-fail.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/solution/bfv-instance-fails-to-migrate-driver-initialize-connection-fail.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.