ImageBuilder PowerCLI cmdlets fail create/clone/modify image profile

Products

• VMware vSphere ESXi

Issue/Introduction

This article aims to explain a difference in the behavior of some cmdlets in the VMware.ImageProfile PowerCLI module.

Symptoms:

Creating/cloning/modifying an image profile with cmdlets from VMware ImageProfile PowerCLI module results in the following error:

"On platform embeddedEsx, Base Image version <new-base-image-version> does not match the base ESXi package version <current-base-image-version> in ImageProfile <image-profile-name>. Use a depot instead of VIB URLs to perform ESXi patching."

Environment

VMware vSphere PowerCLI 13.0
VMware vSphere PowerCLI 13.1
VMware vSphere PowerCLI 13.2

Cause

VMware.ImageBuilder has stricter guards around image profile generation as of the PowerCLI 13.0 release. When upgrading VIBs part of a multi-VIB component, customers need to upgrade all VIBs part of that component. The version of VIBs within the image profile that are part of the ESXi component needs to match the version of the esx-base VIB. The ESXi component needs to match the version of the base image that the image profile was originally created with.

Resolution

Currently there is no resolution.

Workaround:

The work around would be to clone the profile of the target ESXi/esx-base version and upgrade other VIBs as needed to ensure version integrity.