@ -27,6 +27,10 @@ Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a s
.TP
When called without a value, it shows if the boot menu is enabled or not. If called with 'yes', it enables the boot menu. If called with 'no', the boot meny is disabled.
.TP
\fB\-\-boot\-order\fR <dev1,dev2,...,devN>
.TP
When called without a value, it shows if the current order of boot devices. To set a new boot device order, use a comma-separated list of boot devices. Note that any boot devices that are not specified will be moved in their original order to boot after the specified devices are moved up. For this reason, you can just specify the device you want to boot, and it will be moved to the front of the list.
.TP
\fB\-\-job\-uuid\fR
This is the jobs -> job_uuid to execute. Generally this is only used by other programs.
@ -737,6 +737,13 @@ The XML that failed sanity check was:
<keyname="error_0466"><![CDATA[The Anvil! string (name or UUID): [#!variable!string!#] didn't match any known Anvil! in the database.]]></key>
<keyname="error_0467"><![CDATA[[ Error ] - The repartition attemp failed! Reloading the partition table now!]]]></key>
<keyname="error_0468">We need: [#!variable!space_needed!# (#!variable!space_needed_bytes!# Bytes)] from the storage group: [#!variable!storage_group!#], but the requested DR host does not appear to have a volume group in this storage group. Hint, please use 'anvil-manage-storage-groups' to resolve. Unable to proceed.</key>
<keyname="error_0469">[ Error ] - The device: [#!variable!device_target!#] was not found, exiting.</key>
<keyname="error_0470">[ Error ] - The new definition is bad:
========
#!variable!new_server_definition!#
========
[ Error ] - The new definition, shown above failed its test parsing, aborting.</key>
<keyname="error_0471">[ Error ] - There was a problem trying to save the new definition. Details should be in the logs. It's possible the update partially applied.</key>
<!-- Files templates -->
<!-- NOTE: Translating these files requires an understanding of which lines are translatable -->
@ -1706,6 +1713,9 @@ Note: This is a permanent action! If you protect this server again later, a full
<keyname="job_0475">The subnode: [#!variable!subnode!#] is not ready. Configured: [#!variable!configured!#], maintenance mode: [#!variable!maintenance_mode!#], job_running: [#!variable!job_running!#].</key>
<keyname="job_0476">Waiting for a bit, then will check again.</key>
<keyname="job_0477">Waiting for both subnodes to be configured and out of maintenance mode.</key>
<keyname="job_0478">Preparing the new definition file</key>
<keyname="job_0479">The new definition is ready, saving it.</key>
<keyname="job_0480">Running as a job, not prompting the user to confirm.</key>