Error : "The Heat 'build_info' revision is incorrectly configured in the target VIM and is not a semver-compliant format (one or both of api='unknown', engine='unknown')" during scale out.
search cancel

Error : "The Heat 'build_info' revision is incorrectly configured in the target VIM and is not a semver-compliant format (one or both of api='unknown', engine='unknown')" during scale out.

book

Article ID: 446074

calendar_today

Updated On:

Products

VMware Integrated OpenStack

Issue/Introduction

  • When a third-party orchestrator initiates a scale-out or deployment workflow against OpenStack, the following warning is logged:

    "The Heat 'build_info' revision is incorrectly configured in the target VIM and is not a semver-compliant format (one or both of api='unknown', engine='unknown'). Please refer to the VIM vendor's documentation on how to configure this value correctly in your VIM platform.'"

  • The deployment or workflow completes successfully without any impact. 

Environment

VIO 7.0U3

TCP 3.0

Cause

  • This is a cosmetic warning and does not cause any impact.
  • When the external orchestrator connects to OpenStack, it queries the Heat API for its software version (Semantic Versioning, e.g., 1.2.3).
  • Some OpenStack distributions or specific builds return "unknown" for these values rather than a strict numerical version.
  • VIO deploys OpenStack as a series of containerized microservices running on Kubernetes.
  • During VMware's container build process for the heat-api and heat-engine images, the specific Python package version metadata is often stripped.
  • Because "unknown" is not standard semantic formatting, the orchestrator logs a warning and safely assumes a baseline version of "0.0.0" to ensure stability.

Resolution

  • This is an expected cosmetic warning and does not cause any impact.
  • Safely acknowledge the warning and proceed with the scale-out workflow.
  • The orchestrator will successfully build the required resources using the assumed baseline API configuration.