After upgrading Tanzu Isolation Segment to v6.0.17, apps fail with error `GLIBC_2.28' not found (required by /etc/cf-assets/envoy/envoy)

Products

• VMware Tanzu Application Service

Issue/Introduction

This problem occurs after upgrading Tanzu Isolation Segments to v6.0.17. Apps will fail to start and smoke-tests will fail with error such as - 

{{ 2025-06-26T16:20:17.09-0300 [APP/PROC/WEB/0] OUT Invoking start command.
2025-06-26T16:20:17.09-0300 [PROXY/0] ERR /etc/cf-assets/envoy/envoy: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /etc/cf-assets/envoy/envoy)
2025-06-26T16:20:17.09-0300 [PROXY/0] ERR /etc/cf-assets/envoy/envoy: /lib/x86_64-linux-gnu/libpthread.so.0: version `GLIBC_2.30' not found (required by /etc/cf-assets/envoy/envoy)

Apps will fail to start and go into 'failing' state.

Cause

This problem is caused by the version of rootfs shipped with Envoy sidecar in 4.0.37, 6.0.17, 10.0.7 release of Tanzu Platform for Cloud Foundry isolation segment

Resolution

This issue is fixed in versions 4.0.38, 6.0.18, and 10.0.8 of Tanzu Platform for Cloud Foundry isolation segment.

See release notes: [Bug Fix] Pick correct rootfs for sidecar containers

These releases are available for download on Broadcom Support Portal  and can be upgraded by standard upgrade procedure.