openstack/ironic
Code Issues Proposed changes

Merge "[doc] Fix indentation in admin/troubleshooting"

Browse Source
This commit is contained in:
Zuul 2020-06-17 10:24:54 +00:00 committed by Gerrit Code Review
commit 1c0a9c8c28
1 changed files with 13 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
doc/source/admin/troubleshooting.rst
View File

@ -81,7 +81,7 @@ A few things should be checked in this case:
#. Upon scheduling, Nova will query the Placement API service for the #. Upon scheduling, Nova will query the Placement API service for the
available resource providers (in the case of Ironic: nodes with a given available resource providers (in the case of Ironic: nodes with a given
resource class). If placement does not have any allocation candidates for the resource class). If placement does not have any allocation candidates for the
requested resource class, the request will result in a "Nova valid host requested resource class, the request will result in a "No valid host
was found" error. It is hence sensible to check if Placement is aware of was found" error. It is hence sensible to check if Placement is aware of
resource providers (nodes) for the requested resource class with:: resource providers (nodes) for the requested resource class with::
@ -92,20 +92,20 @@ A few things should be checked in this case:
| 1 | CUSTOM_BAREMETAL_LARGE=1 | 2f7b9c69-c1df-4e40-b94e-5821a4ea0453 | CUSTOM_BAREMETAL_LARGE=0/1 | | 1 | CUSTOM_BAREMETAL_LARGE=1 | 2f7b9c69-c1df-4e40-b94e-5821a4ea0453 | CUSTOM_BAREMETAL_LARGE=0/1 |
+---+-----------------------------+--------------------------------------+-------------------------------+ +---+-----------------------------+--------------------------------------+-------------------------------+
For Ironic, the resource provider is the UUID of the available Ironic node. For Ironic, the resource provider is the UUID of the available Ironic node.
If this command returns an empty list (or does not contain the targeted If this command returns an empty list (or does not contain the targeted
resource provider), the operator needs to understand first, why the resource resource provider), the operator needs to understand first, why the resource
tracker has not reported this provider to placement. Potential explanations tracker has not reported this provider to placement. Potential explanations
include: include:
* the resource tracker cycle has not finished yet and the resource provider * the resource tracker cycle has not finished yet and the resource provider
will appear once it has (the time to finish the cycle scales linearly with will appear once it has (the time to finish the cycle scales linearly with
the number of nodes the corresponding ``nova-compute`` service manages); the number of nodes the corresponding ``nova-compute`` service manages);
* the node is in a state where the resource tracker does not consider it to * the node is in a state where the resource tracker does not consider it to
be eligible for scheduling, e.g. when the node has ``maintenance`` set to be eligible for scheduling, e.g. when the node has ``maintenance`` set to
``True``; make sure the target nodes are in ``available`` and ``True``; make sure the target nodes are in ``available`` and
``maintenance`` is ``False``; ``maintenance`` is ``False``;
#. If you do not use scheduling based on resource classes, then the node's #. If you do not use scheduling based on resource classes, then the node's
properties must have been set either manually or via inspection. properties must have been set either manually or via inspection.
@ -163,8 +163,6 @@ A few things should be checked in this case:
check ``openstack hypervisor show <IRONIC NODE>`` to see the status of check ``openstack hypervisor show <IRONIC NODE>`` to see the status of
individual Ironic nodes as reported to Nova. individual Ironic nodes as reported to Nova.
.. TODO(dtantsur): explain inspecting the placement API
#. Figure out which Nova Scheduler filter ruled out your nodes. Check the #. Figure out which Nova Scheduler filter ruled out your nodes. Check the
``nova-scheduler`` logs for lines containing something like:: ``nova-scheduler`` logs for lines containing something like::