> 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/openstack-server-list-command-takes-a-long-time-to-execute.md).

# OpenStack Server List Command Takes a Long Time to Execute

## Problem

When you are trying to query the list of *servers* within a specific *project* or across the entire *region,* it takes a long time to get a response using the *OpenStack\_\_CLI*.

## Environment

* Platform9 Managed OpenStack - All Versions
* *Nova*
* *OpenStack CLI -* v3.12.0 and above

## Cause

When running the *openstack server list* command using *OpenStack CLI*, **GET** calls are also generated to list *Glance\_\_images* as well as all the *flavors* in the region. This is done in batches of 20 and takes a long time if there are a lot of *images* and *flavors* in the *region*. The reason behind querying the *images* and *flavors* is to display names instead of UUIDs in the *server list* output.

## Resolution

1. To avoid long query time, run the *server list* command with the ***--no-name-lookup (-n)***flag. This will not generate any **GET** calls to *Glance* or *Nova* for listing *images* and *flavors* with their names. A few examples are shown below.

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

```javascript
# openstack server list --project <project-ID> --no-name-lookup
# openstack server list --all-projects --no-name-lookup
                  
# openstack server list --project <project-ID> -n
# openstack server list --all-projects -n
```

{% endtab %}
{% endtabs %}

## Additional Information

[Python OpenStack Client v3.12.0 Release Notes](https://docs.openstack.org/releasenotes/python-openstackclient/unreleased.html#relnotes-3-12-0)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://platform9.com/kb/pmo/solution/openstack-server-list-command-takes-a-long-time-to-execute.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.