> 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/how-to/bootable-volume-creation-fails-with-error-key-signature_verifie.md).

# Bootable Volume Creation Fails With Error "key signature\_verified exists for volume

## Problem

The volume creation fails when the volume is being created using an image. The following error is observed in the **cindervolumebase.log** located under ***/var/log/pf9/*** directory.

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

```none
ERROR cinder.volume.flows.manager.create_volume [...] Failed updating volume 446e9e1e-bb79-4a72-bd07-9cb6d492916a metadata using the provided image f136a750-0398-4529-bf23-d01d1582acbe metadata: GlanceMetadataExists: Glance metadata cannot be updated, key signature_verified exists for volume id 446e9e1e-bb79-4a72-bd07-9cb6d492916a
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Cinder

## Cause

The error is observed because **Glance** signature verification is enabled in **Cinder** configuration.

## Resolution

1. Login to the **Cinder** host and add the following property to the *cinder\_override.conf* file under the **DEFAULT** stanza.

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

```none
verify_glance_signatures = disabled
```

{% endtab %}
{% endtabs %}

2. Restart the **pf9-cindervolume-base** service using the following command.

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

```none
service pf9-cindervolume-base restart
```

{% endtab %}
{% endtabs %}


---

# 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 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/how-to/bootable-volume-creation-fails-with-error-key-signature_verifie.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 `automate deployments from our CI pipeline` 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.