Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.12
Component/s: oauth-proxy
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Low
Regression:
No

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

In a FIPS enabled cluster prometheus-proxy is restarting time to time reporting the following error:

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation

We would like to have your help to analyze the stacktrace goroutine reported in the prometheus-proxy logs after the segmentation violation error and before the restart.

Version-Release number of selected component (if applicable):

4.12.40

How reproducible:

Not known, happened at customer cluster.

Steps to Reproduce:

Currently not known how to reproduce it.

Actual results:

prometheus-proxy panics unexpectedly.

Expected results:

prometheus-proxy should be stable.

Additional info:

Before the seg violation also these errors are shown when the prometheus adapters try to connect: 

server.go:3230: http: panic serving IP:port: tls: HKDF-Extract invocation failed unexpectedly

Assignee:: Stanislav Láznička (Inactive)

Reporter:: Christian Passarelli

Need Info From:: None

Contributors:: None

QA Contact:: Junqi Zhao

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2024/06/11 3:10 PM

Updated:: 2025/09/13 11:17 AM

Resolved:: 2025/04/28 10:14 AM