Failed with ERR_SYSTEM_CONFIG_FAILED, message:Step 8 of 43: ERR_SYSTEM_CONFIG_FAILED: Unable

to make a required system

OmniStack 4.0.1 to later.

INFO [c.s.d.o.DeployExecutor] setDeployStatus(DeployExecutor.java:96) -

DeployStatus(status:Running, detail:HVI_CONFIGURING_HYPERVISOR, message:Step 8 of 43:
Configuring hypervisor
Estimated time remaining for completing the current node deployment: 48 minute(s)
The current step will take approximately: 4 minute(s))
ERROR [c.s.d.o.DeployExecutor] setDeployStatus(DeployExecutor.java:94) -
DeployStatus(status:ERROR, detail:ERR_SYSTEM_CONFIG_FAILED, message:Step 8 of 43:
ERR_SYSTEM_CONFIG_FAILED: Unable to make a required system configuration change. - Unspecified
error. See log for details.)
ERROR [c.s.d.o.DeployExecutor] run(DeployExecutor.java:229) -
com.simplivity.deploy.orchestrator.DeployException: ERR_SYSTEM_CONFIG_FAILED: Unable to make a
required system configuration change. - Unspecified error. See log for details.
at
com.simplivity.deploy.orchestrator.DeployActions.checkReadyForReboot(DeployActions.java:635)
at com.simplivity.deploy.orchestrator.DeployStep.run(DeployStep.java:38)
at com.simplivity.deploy.orchestrator.DeployExecutor.run(DeployExecutor.java:215)
at java.lang.Thread.run(Unknown Source)

DM - refers to the Deployment Manager software which is installed and used to deploy the node.
DI - refers to the Deployment Installer, which is mounted as a virtual image & allows the node
be discovered on the network by DM.

One of the reasons of a deployment falling at Step 8, is due to the selection of components i.e.
ESXi & SimpliVity images, that are not compatible with the DM & DI versions used version
being installedfor the deployment.

For instance:
 If the version of DM software installed & DI mounted are different. <--- Is this checked?
 If the versions of DM & DI are older than the release that initially supported required
ESXi version.

Solution

 Always try to use all deploy artifacts ( DM, DI, Omnistack Ova & ESXi tar) from same
release to deploy a new node. Deploy with only the versions included in the deploy
bundle for the particular SimpliVity release.
 If a newer version of an ESXi version is required, then there are 3 2 options:
o Deploy with only the versions included in the deploy bundle & once complete
upgrade to the later ESXi release.
o Upgrade the Omnistack version on the existing nodes to the version that
originally supported ESXi version and then try to add new node to the same
cluster using deployment artifacts from the same release. If not a new deploy,
 upgrade & commit the Cluster to a later SimpliVity software release, that includes
the ESXi version in the deployment bundle.
o Since DM/DI are backward compatible, a Use the DM,DI & ESXi tar from the
version that initially supported required ESXi version along with later version of
DM & DI, can be used with an older version of SimpliVity ova file that matches
existing nodes SimpliVity version.

For example:

If a requirement is the deploy ESXi 7.0U3c with 4.1.0U1, then:

Option1:
Upgrade “Omnistack’ component of existing nodes to 4.1.2
Deploy the new node with deploy artifacts from 4.1.2

Option2:

1. DM & DI from 4.1.2 needs to be installed and mounted, since ESXi 7.0U3c was first
included with this deployment release (4.1.2).

o simplivity-deployment-manager-4.1.2.81.msi
o deploy-installer-11.93.1-psi29+sva-4.1.2.185-usb-tiny.img

2. include only SimpliVity software in the Downloads Folder for 4.1.0U1

o SimpliVity-OmniCube-Image-4.1.0.284-release.ova
o SimpliVity-OmniCube-Image-4.1.0.284-release.ova.sha256
3. Include also in the Downloads Folder ESXi version 7.0U3c
o hypervisorImage-19193900.2-hp.tar
o hypervisorImage-19193900.2-hp.tar.sha256