diff options
author | Julia Kreger <juliaashleykreger@gmail.com> | 2022-07-25 13:20:23 -0700 |
---|---|---|
committer | Julia Kreger <juliaashleykreger@gmail.com> | 2022-07-25 13:20:23 -0700 |
commit | 56d3c5a0311aadf5fce9b80ce2420dc4f1ed4482 (patch) | |
tree | dbf94ccd3e6856b7e1579ecb3f7c520eda2072c3 | |
parent | 4d5c60650efb3fd3af3179d34d2684617a7780ee (diff) | |
download | ironic-56d3c5a0311aadf5fce9b80ce2420dc4f1ed4482.tar.gz |
Clarify disk_label with a warning
Turns out I've had two people try to use disk label
twice in the last week to infer UEFI booting system.
This is not correct, unfortunately.
Clarify that the boot mode needs to be set appropriately.
Change-Id: I515358d40b03ea0d38dad2104a2d3d2c66e0ae8c
-rw-r--r-- | doc/source/install/include/disk-label.inc | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/source/install/include/disk-label.inc b/doc/source/install/include/disk-label.inc index fb144ba37..4a0fa9b02 100644 --- a/doc/source/install/include/disk-label.inc +++ b/doc/source/install/include/disk-label.inc @@ -40,6 +40,12 @@ and sections will describe both methods: * Only one disk label - either ``msdos`` or ``gpt`` - can be configured for the node. +.. warning:: + If the host is in UEFI boot mode, use of ``disk_label`` is redundant, + and may cause deployments to fail unexpectedly if the node is *not* + explicitly set to boot in UEFI mode. Use of appropriate boot mode is + highly recommended. + When used with Compute service ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |