Bug 1731481
| Summary: | failed: waiting for Alertmanager Route to become ready | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Thomas Wiest <twiest> |
| Component: | openshift-apiserver | Assignee: | Stefan Schimanski <sttts> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | alegrand, anpicker, aos-bugs, erooth, gblomqui, jupierce, mfojtik, mloibl, pkrupa, surbania |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | buildcop | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-01 10:42:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Thomas Wiest
2019-07-19 13:53:35 UTC
I'm not seeing any evidence to support the claim that ingress is malfunctioning in this case. The monitoring routes are admitted: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/4230/artifacts/e2e-aws-upgrade/must-gather/namespaces/openshift-monitoring/route.openshift.io/routes.yaml The ingress operator is reporting available: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/4230/artifacts/e2e-aws-upgrade/must-gather/namespaces/openshift-ingress-operator/operator.openshift.io/ingresscontrollers/default.yaml There are no errors in the ingress controller or router logs. The following error is cited in the build log/this Bugzilla: level=fatal msg="failed to initialize the cluster: Cluster operator monitoring is reporting a failure: Failed to rollout the stack. Error: running task Updating Alertmanager failed: waiting for Alertmanager Route to become ready failed: waiting for RouteReady of alertmanager-main: the server is currently unable to handle the request (get routes.route.openshift.io alertmanager-main)" It's not clear to me how that error can be interpreted as evidence of ingress failure. It looks to me like either the endpoint behind the route is returning an error (what is "the server"?), or the apiserver itself can't be reached (why is "get routes.route.openshift.io" present in the error?) Do you agree this is unlikely to be a routing issue? Changing the needinfo to Sergiusz Urbaniak as he's the one that reassigned it to the ingress team. The "routes.route.openshift.io" resource is provided by OpenShift API server. Can you check if the OpenShift API server is running? *** Bug 1721528 has been marked as a duplicate of this bug. *** Thomas, needinfo on you based on comment #6 Michal and Greg, I don't have any additional information. This bug was created while I was build cop and I provided the information that caused this build failure / bug to be created in the original bug description. |