Skip to content

Deprecated: BootEnv Does Not Explode ISO After Upload

Deprecated

This article troubleshoots new or cloned BootEnvs — a pattern that is no longer recommended. Copying or cloning a BootEnv to customize an OS install creates sprawl and is difficult to maintain. Use one of the modern approaches instead:

The original troubleshooting content is retained below for reference by existing deployments.

New or cloned BootEnv does not explode the uploaded ISO components in Digital Rebar after upload (eg drpcli bootenvs upload iso <BOOTENV>, or drpcli isos upload <ISO>).

Solution

Possible Causes:

  1. Uploaded ISOs must match shasums (sha256sum) listed in the BootEnv
  2. Install BootEnvs must end in -install. See BootEnv
  3. BootEnvs intended for network booting, must include netbootable components
  4. The ISO Filename that is uploaded must exactly match the BootEnv specified name

Additional Information

Additional resources and information related to this Knowledge Base article.

See Also

Versions

all

Keywords

content pack, bootenv, iso, sha256sum, deprecated, clone, copy, bootenv-customize, override

Revision Information

Text Only
KB Article     :  kb-00032
initial release:  Wed Jun 10 12:31:44 PDT 2020
updated release:  Tue Jun 16 2026 (deprecated; superseded by bootenv override / universal replacement)