Stateful AutoDeploy does not create a local datastore
search cancel

Stateful AutoDeploy does not create a local datastore

book

Article ID: 385783

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

When using AutoDeploy with host profile set to statefull install on the local hard drive, host profile task fails during boot and does not create a local datastore.

syslog.log may show similar entries:

<YYYY-MM-DD>T<time>Z Wa(12) hostprofile[2100874]: opID=MainThread: excObj is a runtime fault: (vim.fault.RestrictedVersion) {
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:    dynamicType = <unset>,
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:    dynamicProperty = (vmodl.DynamicProperty) [],
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:    msg = 'Current license or ESXi version prohibits execution of the requested operation.',
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:    faultCause = <unset>,
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:    faultMessage = (vmodl.LocalizableMessage) [
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:       (LocalizableMessageWithPath) {
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:          dynamicType = <unset>,
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:          dynamicProperty = (vmodl.DynamicProperty) [],
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:          key = 'com.vmware.vim.profile.engine.UnexpectedError',
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:          arg = (vmodl.KeyAnyValue) [
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:             (vmodl.KeyAnyValue) {
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                dynamicType = <unset>,
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                dynamicProperty = (vmodl.DynamicProperty) [],
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                key = 'error',
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                value = 'Current license or ESXi version prohibits execution of the requested operation.'
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:             },
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:             (vmodl.KeyAnyValue) {
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                dynamicType = <unset>,
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                dynamicProperty = (vmodl.DynamicProperty) [],
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                key = 'context',
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:                value = 'EngineModule::ApplyHostConfig'
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:             }
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:          ],
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:          message = 'Error: Current license or ESXi version prohibits execution of the requested operation..'
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:       }
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]:    ]
<YYYY-MM-DD>T<time>Z Wa(12)[+] hostprofile[2100874]: }^@
<YYYY-MM-DD>T<time>Z In(14) hostprofile[2100874]: opID=MainThread: Cleaned up Host Configuration^@
<YYYY-MM-DD>T<time>Z In(14) hostprofile[2100874]: opID=MainThread: /sbin/applyHostProfile sending boot msg to console: Applying Host Profile task list...Error^@
<YYYY-MM-DD>T<time>Z Er(11) hostprofile[2100874]: opID=MainThread: while applying tasks: (vim.fault.RestrictedVersion) {

Environment

VMware vCenter Server 8.0 U3

Cause

During the boot process, AutoDeploy uses either an assigned license or an evaluation license. The evaluation license period is calculated based on hardware identifiers of the host. If the host was first booted years ago, subsequently removed from inventory, and finally rebooted, AutoDeploy assumes that the evaluation license has expired. AutoDeploy lacks a mechanism to request a new license during the boot process, resulting in errors during the application of the host profile.

In versions prior to 8.0.2, the license check mechanism did not properly handle this workflow.

Resolution

Recommendation:

  • Do not remove the ESXi host from the vCenter inventory before performing the operation.
  • If the ESXi host has previously been provisioned using AutoDeploy, simply select the host in the vCenter inventory and use the "Remediate Host" option available under the deployed hosts tab.

If the AutoDeploy host has been removed from the vCenter inventory and requires to join the vCenter after autodeploy boot:

  • Re-apply the host profile after ESXi host joins vCenter cluster.
  • Reboot the host.

 

Additional Information

This issue will be fixed in future release of vCenter 8.0

Powered by Wolken Software