Skip to main content

​
DRY_RUN & Validation

The installer family is designed to make host changes visible before execution.

​
DRY_RUN

DRY_RUN defaults to enabled. When DRY_RUN=1:
  • commands are displayed rather than executed
  • the operator still sees the normal confirmation flow
  • destructive/system-changing commands are not executed
  • the workflow can be inspected in the same step order as real execution
DRY_RUN is not a substitute for reviewing the target host. It helps expose intended changes but cannot prove that every production dependency will behave identically.

​
Full Configuration Validation

Validation is read-only and checks the active environment and configuration. The common result model is:
  • OK — requirement satisfied
  • WARN — review or recommendation
  • FAIL — blocking problem
A FAIL must be corrected before deployment.
1

Run with DRY_RUN enabled

Walk through the selected installer and verify detected NICs, disks, versions, image inputs and VM parameters.
2

Run Full Configuration Validation

Resolve every blocking result and review warnings.
3

Confirm recovery access

Ensure console/out-of-band access and rollback or recovery procedures are available.
4

Disable DRY_RUN only for the approved execution

Re-check the configuration summary before confirming system-changing steps.
Last modified on September 22, 2026