Skip to main content

Cannot deploy an operating system

Use this information to troubleshoot general issues that you might encounter when you attempt to deploy an operating system to a managed server from Lenovo XClarity Administrator.

Known limitation
In slow network environments, operating-system deployment of SLES 12 and 12.1 in static IP mode might fail because the network delay boot parameter does not take effect in that mode. This is issue is fixed in SLES 12.2.
Complete the following steps to resolve the issue:
  1. For servers with XCC2 that have System Guard enabled and the action set to Prevent OS booting, ensure that System Guard is compliant on the device. If System Guard is not compliant, the devices are prevented from completing the boot process, which causes the OS deployment to fail. To provision these devices, manually respond to the System Guard boot prompt to allow the devices to boot normally.

  2. If you see the https://<management_server_IP>/osdeployment/connection/… Permission denied message, update the BIOS on the server, and change the date and time setting to the current date and time.

  3. Review all requirements for the operating system that is being deployed. See Supported operating systems.
    For example:
    • An issue can occur with the deployment of VMware ESXi if you do not set the Memory Mapped I/O (MMIO) space to at least 3 GB.
    • If you are deploying Microsoft Windows and joining an Active Director domain, follow the considerations that are described in Integrating with Windows Active Directory.
  4. Review operation-system deployment support limitations for specific I/O adapters. For information about I/O adapter support, see the XClarity Administrator Support – Compatibility webpage.

  5. Ensure that you have a stable network connection between XClarity Administrator and the device (managed server) on which the operating system is going to be installed.
    Note
    When deploying SLES 11 SP4, the deployment might stop and not restart if the network connection is lost between XClarity Administrator and the device. If this occurs, check your network environment, and redeploy the operating system.
  6. Ensure that at least one network port on XClarity Administrator is set to manage and deploy operating-system images.

    You can configure the XClarity Administrator network topology from the Network Access page. For more information about the Network Access page, see Configuring network access.

  7. Ensure the XClarity Administrator network port that is being used to attach to the data network is configured to be on the same network as the data network ports on the managed server. The server’s port is specified by the MAC Address and is configurable through the Operating Systems -> Network Settings page. For more information about editing network settings, see Configuring network settings for managed servers.
  8. Ensure that the target server does not have a deferred or partially activated server patter. If a server pattern has been deferred or partially activated on the target server, restart the server to apply all configuration settings.
  9. View the status of the server from the Deploy OS Images page to ensure that it has a deployment status of Ready. If the status is Not Ready, click the status link to determine why the server is not ready for operating-system deployment.

    For more information about operating-system deployment, see Deploying an operating-system image.

  10. Ensure that the device has visibility to the storage location that was selected for operating-system deployment.
    Tip
    To ensure that operating-system deployments are successful, detach all storage from the server except the storage chosen for the operating-system deployment.