> 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/healthy-instance-with-os-ext-sts-fault-populated.md).

# Healthy Instance With OS-EXT-STS:fault Populated

## Problem

An instance has recovered from any number of issues which might have caused the ***OS-EXT-STS:fault*** field to be populated with an error message. The error remains in place though the instance appears to be functioning as expected.

**Example**:

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

```none
[root@pf9 ~(admin)]# openstack server show 2936e2b4-3e58-467e-9831-c51450a6afdb+-------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+| Field | Value |+-------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+| OS-DCF:diskConfig | MANUAL || OS-EXT-AZ:availability_zone | || OS-EXT-PF9-SRV-RES-INFO:res_info | {u'cfg_disk_gb': 20.0, u'vcpus': 1, u'cfg_memory_mb': 2048, u'cpu_mhz': 1000} || OS-EXT-SRV-ATTR:host | None || OS-EXT-SRV-ATTR:hypervisor_hostname | None || OS-EXT-SRV-ATTR:instance_name | 2936e2b4-3e58-467e-9831-c51450a6afdb || OS-EXT-STS:fault | {u'message': u'Build of instance 2936e2b4-3e58-467e-9831-c51450a6afdb aborted: Block Device Mapping is Invalid.', u'code': 500, u'details': u' File "/opt/pf9/venv/lib/python2.7/site-packages/nova/compute/manager.py", line 1958, in _do_build_and_run_instance<br> filter_properties)<br> File "/opt/pf9/venv/lib/python2.7/site-packages/nova/compute/manager.py", line 2124, in _build_and_run_instance<br> \'create.error\', fault=e)<br> File "/opt/pf9/venv/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__<br> self.force_reraise()<br> File "/opt/pf9/venv/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise<br> six.reraise(self.type_, self.value, self.tb)<br> File "/opt/pf9/venv/lib/python2.7/site-packages/nova/compute/manager.py", line 2086, in _build_and_run_instance<br> block_device_mapping) as resources:<br> File "/opt/pf9/python/lib/python2.7/contextlib.py", line 17, in __enter__<br> return self.gen.next()<br> File "/opt/pf9/venv/lib/python2.7/site-packages/nova/compute/manager.py", line 2251, in _build_resources<br> reason=e.format_message())<br>'} |
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v3.6.0 and Higher
* Nova

## Resolution

This is a known bug and there is currently no known workaround or resolution to this issue; however, rest assured, our Engineering teams will be addressing the problem in a future release. We will update this article as additional information becomes available.


---

# 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/solution/healthy-instance-with-os-ext-sts-fault-populated.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.