> 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/heat-stack-creation-fails-with-error-no-images-matching.md).

# Heat Stack Creation Fails With Error "No images matching

## Problem

The heat stack creation fails with the following error observed in the Heat API log.

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

```none
008.008 12030 INFO heat.engine.stack [req-UUID - tanium-class - default default] Stack CREATE FAILED (coffeepot): Resource CREATE failed: resources.uuzm4ovvxzun: resources.scaleup_group.Property error: resources.volume.properties.image: Error validating value 'cirros.img': No images matching {'name': u'cirros.img'}.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v3.6.0 and Higher

## Cause

* The image being used in the creation of the heat stacks has its ***visibility*** set to ***shared***.
* This value is set by default if no visibility value like ***public*** or ***private*** is not provided.

## Resolution

* Set the OpenStack image visibility to ***public*** using the following command.

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

```none
openstack set image --public [IMAGE UUID]
```

{% endtab %}
{% endtabs %}

## Additional Information

[Image Service API v2](https://docs.openstack.org/api-ref/image/v2/)


---

# 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/how-to/heat-stack-creation-fails-with-error-no-images-matching.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.