Configuration Changes Requiring Re-installation

Some configuration changes require a system or host re-add.

Table 1. Configuration Changes Requiring Reinstallation

Change	Reinstall	Comments
Product type change	System	To change between Standard and All-in-one, you must perform a system reinstallation.
PXE boot network addition or removal	System	You must perform a system reinstallation.
Management network subnet or range changes	System	You must perform a system reinstallation.
Cluster-host subnet or range changes	System	You must perform a system reinstallation.
Legacy BIOS to UEFI change	System	You must perform a system reinstallation.
Security profile change	System	You must perform a system reinstallation.
Controller filesystem size decrease	System	To decrease the controller filesystem size, you must perform a system reinstallation.
Root disk replacement	Host (re-add)	To install the OpenStack application on a new disk, the host must be deleted and re-added (not merely reinstalled).
Replacement of storage disk on SAS controller	Host (re-add)	Due to a limitation in udev, the device path of a disk connected through a SAS controller changes when the disk is replaced. You must lock, delete, and re-install the node. Once this is done, it is advisable to replace any storage profiles associated with the host, since the old storage profile is no longer accurate.
Aborted upgrade after controller-1 and controller-0 upgraded	System	You must perform a system reinstallation.
Subcloud delete and re-add	System	The subcloud system must be reinstalled.
Configuration commands run from SSH	System	An error occurs if any of the sw-patch install-local command is run from an SSH session. To recover, you must reinstall the system.
Developer certificate or update removal	System	Required to correct Alarm 500.100
Management network netmask correction on a Duplex system	System	On a Duplex system, the minimum management netmask is /28.
Host version mismatch	Host (re-add)	Required to correct Alarm 900.003 Note To register the new software version for Host Inventory management, the host must be deleted and re-added (not merely reinstalled)
Host memory module addition or removal	Host (re-add)	For example, use system host-delete, followed by system host-add, or system host-update, as the host may be re-added automatically by the system on discovery. Optionally, with Deployment Manager, follow the Node replacement procedure.