Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-11284

Segmentation fault in proxy on FIPS cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • OSSM 3.2.0
    • OSSM 3.2.0
    • Envoy
    • None

      There is segmentation fault in `istio-proxy` container (ingress gateway or proxy sidecars) on the OSSM 3.2.0 release candidate when running on FIPS cluster.

      /root/.cache/bazel/_bazel_root/530ed184f85848d5a11a3a8203c74c1b/sandbox/processwrapper-sandbox/997/execroot/io_istio_proxy/external/envoy/bssl-compat/source/RSA_check_fips.cc:6 RSA_check_fips() NYI
      2025-11-06T07:30:27.121826Z    warning    envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_stream.h:187    StreamSecrets gRPC config stream to sds-grpc closed: 13, upstream_reset_after_response_started{connection_termination}    thread=14
      2025-11-06T07:30:27.121874Z    warning    envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_stream.h:187    StreamSecrets gRPC config stream to sds-grpc closed: 13, upstream_reset_after_response_started{connection_termination}    thread=14
      2025-11-06T07:30:27.121975Z    warning    envoy config external/envoy/source/extensions/config_subscription/grpc/grpc_stream.h:187    DeltaAggregatedResources gRPC config stream to xds-grpc closed: 13, upstream_reset_after_response_started{connection_termination}    thread=14
      2025-11-06T07:30:27.122054Z    critical    envoy backtrace external/envoy/source/server/backtrace.h:129    Caught Segmentation fault, suspect faulting address 0x0    thread=14
      2025-11-06T07:30:27.122078Z    critical    envoy backtrace external/envoy/source/server/backtrace.h:113    Backtrace (use tools/stack_decode.py to get line numbers):    thread=14
      2025-11-06T07:30:27.122101Z    critical    envoy backtrace external/envoy/source/server/backtrace.h:114    Envoy version: 875f3c95813ea54932036ae11d956d773063d607/1.35.7-dev/3.2.0/RELEASE/OpenSSL    thread=14
      2025-11-06T07:30:27.122121Z    critical    envoy backtrace external/envoy/source/server/backtrace.h:116    Address mapping: 562b2e11a000-562b32f81000 /usr/local/bin/envoy    thread=14 

      The full log and pod yaml are in the attachments.

              tpoole@redhat.com Ted Poole
              mkralik@redhat.com Matej Kralik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: