From ba9f4b3ed4e95f80978277d532f76cbf4e38fe47 Mon Sep 17 00:00:00 2001 From: Lance Bragstad Date: Thu, 16 Jan 2020 13:31:25 -0600 Subject: [PATCH] Clarify HostnameMap keys and how they should match HostnameFormatDefault I hit a hiccup doing a pre-provisioned deployment because my HostnameMap keys were inconsistent with the HostnameFormatDefault specified in the overcloud roles. This commit adds a short snippet to the deployed server documentation that clarifies this detail, just in case people are overriding HostnameFormatDefault for some reason. Change-Id: Ice86379d7b0d0c7cbca1d17bbd3f981303ee216b --- deploy-guide/source/features/deployed_server.rst | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/deploy-guide/source/features/deployed_server.rst b/deploy-guide/source/features/deployed_server.rst index e9772d4e..4a617826 100644 --- a/deploy-guide/source/features/deployed_server.rst +++ b/deploy-guide/source/features/deployed_server.rst @@ -264,7 +264,17 @@ value:: overcloud-novacompute-2: compute-02-rack01 Write the contents to an environment file such as ``hostnamemap.yaml``, and -pass it the environment as part of the deployment command. +pass it the environment as part of the deployment command. It's imperative that +the ``HostnameMap`` keys correspond to the ``HostnameFormatDefault`` for the +appropriate role. For example, using ``overcloud-controller-0`` matches +``HostnameFormatDefault: '%stackname%-controller-%index%'`` in the +``Controller`` role. Similarly, ``overcloud-novacompute-0`` matches +``HostnameFormatDefault: '%stackname%-novacompute-%index%'`` for the +``Compute`` role. If you decide to change the ``HostnameFormatDefault`` to a +different value, you'll need to account for this in your ``hostnamemap.yaml`` +file. Mismatched values between the ``HostnameMap`` keys and +``HostnameFormatDefault`` causes failures during overcloud installation because +TripleO can't find the appropriate hosts, as it's using the wrong names.