Bug 2109731
| Summary: | alertmanager-main pods failing to start due to startupprobe timeout | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Monitoring | Assignee: | Sunil Thaha <sthaha> |
| Status: | CLOSED ERRATA | QA Contact: | hongyan li <hongyli> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.10 | CC: | anpicker, bbennett, dacarpen, diflores, hongyli, mmasters, rauferna, rfredette, spasquie, sthaha, vjaypurk, wking |
| Target Milestone: | --- | ||
| Target Release: | 4.11.z | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-23 15:09:07 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2083226 | ||
| Bug Blocks: | 2108439 | ||
|
Comment 1
Simon Pasquier
2022-07-22 09:20:03 UTC
*** Bug 2108439 has been marked as a duplicate of this bug. *** We have no HPE ProLiant BL460c Gen10, test with arm bare mental cluster versioned-installer-arm_bm-disconnected-ci
Install payload 4.11.0-0.nightly-arm64-2022-08-12-000539
Bound PV to alarm pod
No regression found.
# oc -n openshift-monitoring get po alertmanager-main-0 -oyaml|grep -A10 startupProbe
startupProbe:
exec:
command:
- sh
- -c
- exec curl --fail http://localhost:9093/-/ready
failureThreshold: 40
initialDelaySeconds: 20
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 3
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.11.1 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6103 |