Loading...
Loading...
After a Dell Private Cloud Node Add deployment fails, the operator edits inputs and resumes the failed deployment. During uninstall of the failed run, the system de‑registers the cluster license unexpectedly. Subsequent license expansion (for example, adding capacity/nodes) fails because the cluster license was removed. Repro steps Deploy a cluster using DPC Cluster Deploy blueprint. Perform DPC Node Add . Node Add fails . Update input fields and resume the deployment. The license is de‑registered during uninstall of the failed run.
The license plugin used the default life cycle of the blueprint; when the blueprint was edited and the user did not clear the Uninstall workflow, the de‑registration API was invoked as part of uninstall. As implemented, the license plugin’s de‑registration logic was too broad and applied at cluster scope , causing unintended cluster license removal during recovery from a failed Node Add .
Short‑term fix (implemented and released): The deregistered API has been hardened to no‑op and return HTTP 204 unless the explicit query parameter deleteAllowed=true is provided. This prevents accidental cluster license de‑registration during Uninstall when resuming failed runs. Fixed in the next available Dell Automation Platform release v2.0.0.0 Action: Upgrade to a fixed build to prevent recurrence. Planned long‑term improvement: Engineering revisits the plugin design around de‑register semantics and life cycle coupling to avoid cluster‑wide impacts from component‑level recovery flows.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.