Tanzu Hub Installation Failure - Kubelet "Unknown Command" Error

Products

• Operations Manager
• VMware Tanzu Platform - Hub

Issue/Introduction

During the installation of the Tanzu Hub 10.2.1 tile, the BOSH deployment fails during the updating instance phase of multiple VMs. The BOSH task times out during the kubelet start process, and logs indicate that the node is unable to register itself with the internal Kubernetes cluster, eventually failing with the message:

kubelet.stderr.log

E0203 18:56:04.239935 21024 run.go:72] "command failed" err="unknown command Sets"

Environment

Platform: Tanzu Operations Manager v3.2

Product: Tanzu Hub 10.2.1

Infrastructure: Azure (utilizing Availability Sets)

Cause

The root cause is a string parsing error in the kubelet startup script. The script passes node labels to the kubelet via the --node-labels flag. If the user is using Availability Sets on Azure or an Availability Zone name in the BOSH Director configuration contains a space (e.g., "Availability Sets"), the shell interprets the second word as a standalone command rather than a label value.

Resolution

Fixed in Hub v10.4.0, this is currently planned to be released at the end of April.