Jenkins Fails to Initialize with UnknownAttributesException (imagePullPolicy) Following Helm Chart Upgrade
search cancel

Jenkins Fails to Initialize with UnknownAttributesException (imagePullPolicy) Following Helm Chart Upgrade

book

Article ID: 439597

calendar_today

Updated On:

Products

VMware Tanzu Platform - Kubernetes

Issue/Introduction

An upgrade of the Jenkins Helm chart has introduced a critical initialization failure when using the Jenkins Configuration as Code (JCasC) plugin. Following an update to versions 13.17.0/13.17.1, Jenkins instances may fail to start, throwing an UnknownAttributesException related to an unsupported imagePullPolicy attribute within the container template configuration. This issue prevents the Configuration as Code plugin from successfully applying settings, effectively blocking Jenkins from reaching a ready state.

Environment

  • Product: VMware Tanzu Application Platform (TAP-SM) / VMware Tanzu Platform for Kubernetes

  • Component: Jenkins (deployed via Helm)

  • Plugin: Jenkins Configuration as Code (JCasC)

  • Versions affected: Jenkins Helm Chart 13.17.0 and 13.17.1

  • Versions fixed: Jenkins Helm Chart 13.18.0

Cause

A regression was introduced in the casc-cm.yaml template of the Jenkins Helm chart (specifically between versions 13.15.0 and 13.17.1). The imagePullPolicy attribute was added to the containerTemplate section of the Configuration as Code (CasC) manifest. However, the version of the JCasC plugin or the underlying Kubernetes plugin within the Jenkins distribution does not support imagePullPolicy as a valid attribute for the containerTemplate class, leading to a validation failure during the initialization phase.

Resolution

To resolve this issue, upgrade the Jenkins Helm chart to version 13.18.0. This version contains the official fix that restores compatibility with the JCasC configuration.

Additional Information

If an immediate upgrade to 13.18.0 is not possible, a temporary workaround involves manually editing the casc-cm.yaml template to remove the unsupported imagePullPolicy line, though upgrading to the official patched release is the recommended path.