Bug 1639082 - [3.7] endpoint for alertmamager and alert-buffer gave HTTP response to HTTPS client
Summary: [3.7] endpoint for alertmamager and alert-buffer gave HTTP response to HTTPS ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 3.7.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.7.z
Assignee: Paul Gier
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1638658
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-15 02:55 UTC by Junqi Zhao
Modified: 2019-11-21 18:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1638658
Environment:
Last Closed: 2019-11-21 18:37:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
gave HTTP response to HTTPS client (238.88 KB, image/png)
2018-10-15 02:59 UTC, Junqi Zhao
no flags Details
endpoints for alertmamager and alert-buffer are removed from kubernetes-service-endpoints (125.16 KB, image/png)
2018-11-05 02:39 UTC, Junqi Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1546033 0 unspecified CLOSED Promtheus ansible playbook install results in oauthproxy errors and 3 out of 5 kubernetes-service-endpoints DOWN 2021-02-22 00:41:40 UTC

Internal Links: 1546033

Description Junqi Zhao 2018-10-15 02:55:53 UTC
+++ This bug was initially created as a clone of Bug #1638658 +++

Description of problem:
Deploy prometheus v3.9.45-1

# oc -n openshift-metrics get pod -o wide
NAME                             READY     STATUS    RESTARTS   AGE       IP               NODE
prometheus-0                     6/6       Running   0          3h        10.2.2.4         share3-wmengr76o39-master-etcd-2
prometheus-node-exporter-25v67   1/1       Running   0          3h        192.168.100.14   share3-wmengr76o39-nrri-1
prometheus-node-exporter-9v6gs   1/1       Running   0          3h        192.168.100.12   share3-wmengr76o39-master-etcd-3
prometheus-node-exporter-bkn67   1/1       Running   0          3h        192.168.100.20   share3-wmengr76o39-node-primary-3
prometheus-node-exporter-d9wfc   1/1       Running   0          3h        192.168.100.8    share3-wmengr76o39-node-primary-1
prometheus-node-exporter-fnngw   1/1       Running   0          3h        192.168.100.9    share3-wmengr76o39-nrri-2
prometheus-node-exporter-g7km9   1/1       Running   0          3h        192.168.100.4    share3-wmengr76o39-master-etcd-1
prometheus-node-exporter-jlf2v   1/1       Running   0          3h        192.168.100.16   share3-wmengr76o39-node-primary-2
prometheus-node-exporter-k986p   1/1       Running   0          3h        192.168.100.7    share3-wmengr76o39-master-etcd-2


Checked the targets, Endpoints for alertmamager and alert-buffer are down
target for alertmamager and alert-buffer gave HTTP response to HTTPS client.

# oc -n openshift-metrics rsh prometheus-0
sh-4.2$ curl -k https://10.2.2.4:9093/metrics 
curl: (35) SSL received a record that exceeded the maximum permissible length.

Test with http, thers are metrics output
sh-4.2$ curl -k http://10.2.2.4:9093/metrics
# HELP alertmanager_alerts How many alerts by state.
# TYPE alertmanager_alerts gauge
alertmanager_alerts{state="active"} 0
alertmanager_alerts{state="suppressed"} 0
# HELP alertmanager_alerts_invalid_total The total number of received alerts that were invalid.
# TYPE alertmanager_alerts_invalid_total counter
alertmanager_alerts_invalid_total 0
# HELP alertmanager_build_info A metric with a constant '1' value labeled by version, revision, branch, and goversion from which alertmanager was built.
# TYPE alertmanager_build_info gauge
................................................................................


Version-Release number of selected component (if applicable):
prometheus v3.9.45-1

How reproducible:
Always

Steps to Reproduce:
1. Deploy prometheus v3.9.45-1 and check /targets page
2.
3.

Actual results:
endpoint for alertmamager and alert-buffer gave HTTP response to HTTPS client

Expected results:
endpoint should are in UP state

Additional info:

Comment 1 Junqi Zhao 2018-10-15 02:57:17 UTC
prometheus version: v3.7.68-1

Comment 2 Junqi Zhao 2018-10-15 02:59:12 UTC
Created attachment 1493893 [details]
gave HTTP response to HTTPS client

Comment 3 Paul Gier 2018-10-17 14:42:46 UTC
PR to 3.7: https://github.com/openshift/openshift-ansible/pull/10428

Comment 4 Paul Gier 2018-11-02 14:42:43 UTC
Fixed in 3.7.70.

Comment 5 Junqi Zhao 2018-11-05 02:38:29 UTC
endpoints for alertmamager and alert-buffer are removed from kubernetes-service-endpoints
openshift-ansible:openshift-ansible-3.7.71-1

Comment 6 Junqi Zhao 2018-11-05 02:39:10 UTC
Created attachment 1501594 [details]
endpoints for alertmamager and alert-buffer are removed from kubernetes-service-endpoints


Note You need to log in before you can comment on or make changes to this bug.