using:

abctl local install --chart-version 1.5.1 --verbose

error:

DEBUG   airbyte-bootloader: 2026-02-20 13:47:23,931 [main]    ERROR   i.a.b.Application(main):32 - Unable to bootstrap Airbyte environment.
  DEBUG   airbyte-bootloader: java.lang.RuntimeException: com.fasterxml.jackson.core.JsonParseException: Invalid numeric value: Leading zeroes not allowed
  DEBUG   airbyte-bootloader:  at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 2]
  DEBUG   airbyte-bootloader: Caused by: com.fasterxml.jackson.core.JsonParseException: Invalid numeric value: Leading zeroes not allowed
  DEBUG   airbyte-bootloader:  at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 2]
  DEBUG   airbyte-bootloader:
  DEBUG   airbyte-bootloader: 2026-02-20 13:47:23,940 [Thread-2]        INFO    i.m.r.Micronaut(lambda$start$0):118 - Embedded Application shutting down
  DEBUG   done streaming bootloader logs
  DEBUG   helm: Add/Modify event for airbyte-abctl-airbyte-bootloader: MODIFIED
  DEBUG   helm: warning: Upgrade "airbyte-abctl" failed: pre-upgrade hooks failed: 1 error occurred:
                * pod airbyte-abctl-airbyte-bootloader failed
  DEBUG   helm: release upgrade failed: pre-upgrade hooks failed: 1 error occurred:
                * pod airbyte-abctl-airbyte-bootloader failed
  ERROR   Failed to install airbyte/airbyte Helm Chart
  DEBUG   looking at airbyte-abctl-airbyte-bootloader
            Failed()
  DEBUG   found logs:  Unsetting empty environment variable 'AB_INSTANCE_
  DEBUG   looking at airbyte-abctl-connector-builder-server-68b946f5d4-j62gn
            Running()
  DEBUG   found logs:  Unsetting empty environment variable 'OTEL_COLLECT
  DEBUG   looking at airbyte-abctl-cron-59f8597f69-wgbww
            Running()
  DEBUG   found logs:  Unsetting empty environment variable 'OTEL_COLLECT
  DEBUG   looking at airbyte-abctl-server-69fcc6444b-q85nd
            Running()
  DEBUG   found logs:  Unsetting empty environment variable 'AIRBYTE_URL'
  DEBUG   looking at airbyte-abctl-temporal-6dfb57c666-jqs6t
            Running()
  DEBUG   found logs:  TEMPORAL_ADDRESS is not set, setting it to 0.0.0.0
  DEBUG   looking at airbyte-abctl-worker-5fff5c5796-f7865
            Running()
  DEBUG   found logs:  Unsetting empty environment variable 'ACTIVITY_MAX
  DEBUG   looking at airbyte-abctl-workload-api-server-d869f6994-9qn9x
            Running()
  DEBUG   found logs:  Unsetting empty environment variable 'OTEL_COLLECT
  DEBUG   looking at airbyte-abctl-workload-launcher-687cf6c89b-p4p78
            Pending()
  DEBUG   failed to get pod logs: unable to get logs for pod airbyte-abctl-workload-launcher-687cf6c89b-p4p78: container "airbyte-workload-launcher-container" in pod "airbyte-abctl-workload-launcher-687cf6c89b-p4p78" is waiting to start: CreateContainerConfigError
  DEBUG   looking at airbyte-db-0
            Running()
  DEBUG   found logs:
          PostgreSQL Database directory appears to contain
  DEBUG   looking at airbyte-minio-0
            Running()
  DEBUG   found logs:
           You are running an older version of MinIO releas
  ERROR   Unable to install Airbyte locally
  DEBUG   Event watcher completed.
  ERROR   unable to install airbyte chart: bootloader failed

The knowledge sources show the exact same bootloader error (

JsonParseException: Invalid numeric value: Leading zeroes not allowed

) happening on recent Airbyte Community versions deployed with

abctl

. [[Failed deploy 1.6.1](https://github.com/airbytehq/airbyte/issues/59177); [Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587)] However, they do not document a concrete root cause or fix yet; it’s being discussed as an open issue and the logs are partially redacted, so we can’t see which value is invalid. Because of that, I can’t reliably tell you what in your environment or config is triggering the JSON parse error. What we do know from the docs and issues: - When

airbyte-abctl-airbyte-bootloader

fails,

abctl

reports

pod airbyte-abctl-airbyte-bootloader failed

and the Helm upgrade fails. [[Troubleshooting abctl](https://docs.airbyte.com/platform/deploying-airbyte/troubleshoot-deploy)] - Bootloader failures are “generally related to problem of

airbyte-bootloader

not able to connect to the

airbyte-db

service” or to bad configuration, but the specific “leading zeroes not allowed” JSON error is not yet explained in the docs. [[Troubleshooting abctl](https://docs.airbyte.com/platform/deploying-airbyte/troubleshoot-deploy); [Failed deploy 1.6.1](https://github.com/airbytehq/airbyte/issues/59177)] Given these limitations, here’s what you can concretely do next, based only on what’s in the sources: 1. Confirm this is the same known issue Your log snippet matches the pattern from the 1.6.0/1.6.1 failures: -

Unable to bootstrap Airbyte environment.

-

JsonParseException: Invalid numeric value: Leading zeroes not allowed

- Bootloader pod fails and Helm upgrade aborts. [[Failed deploy 1.6.1](https://github.com/airbytehq/airbyte/issues/59177); [Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587)] This strongly suggests you’re hitting the same class of bug, even though you’re on chart

1.5.1

. 2. Check bootloader logs in full

abctl

v0.15.0+ prints bootloader logs to help understand the cause. [[Troubleshooting abctl](https://docs.airbyte.com/platform/deploying-airbyte/troubleshoot-deploy)] Run (inside the

abctl

cluster context):

bash    kubectl logs deployment/airbyte-abctl-airbyte-bootloader

or, if it’s a pod:

bash    kubectl logs pod/<airbyte-abctl-airbyte-bootloader-pod-name>

The knowledge sources redact the JSON payload, so I can’t see which field is invalid; you’ll need to inspect that locally. 3. Look for a mis‑formatted numeric value with leading zeros From the error message alone, it’s almost certainly a JSON field that looks like

0123

instead of

"0123"

or

123

. But the sources do not say whether this comes from: -

values.yaml

-

secret.yaml

- environment variables - or internal state in the DB So I can’t point to a specific key. You’ll need to: - Review any custom

values.yaml

/

--values

you’re using for numeric fields that might have leading zeros (ports, timeouts, IDs, etc.). - Do the same for any JSON you may have put into secrets or config. Unfortunately, the knowledge sources don’t provide an example of the offending field. 4. Consider using a different chart version In a separate bootloader‑failure thread, a user reports that downgrading the chart version made installation work again:

bash    abctl local install --chart-version=1.7.2

which resolved their

pod airbyte-abctl-bootloader failed

issue. [[Helm chart broken](https://github.com/airbytehq/airbyte/issues/65129)] While this is about a different failure, it shows that chart version changes can work around bootloader problems. The docs don’t state which version fixes the “leading zeroes” JSON bug, so I can’t recommend a specific target version with confidence—only that trying another supported chart version is a documented workaround pattern. 5. If nothing obvious shows up Since the docs explicitly mark bootloader failures as “Status: Investigating” and don’t yet document this JSON bug, the next step is to share: - The full bootloader logs (with the JSON snippet if possible) - Your

abctl

command and any

--values

/

--secret

files in a GitHub issue or the Airbyte Slack, referencing the existing issues: [[Failed deploy 1.6.1](https://github.com/airbytehq/airbyte/issues/59177); [Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587)] Because the knowledge sources don’t contain a confirmed fix or the exact mis‑configured field, I can’t give you a precise one‑line change to make. The most grounded actions, based on the available information, are: - Inspect full bootloader logs for the exact JSON it’s trying to parse. - Remove or correct any numeric values with leading zeros in your config/secrets. - Try a different chart version if you suspect a regression in 1.5.1.