Bug 1625510
| Summary: | [3.11]router targets is down in prometheus targets UI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> | ||||
| Component: | Networking | Assignee: | Dan Mace <dmace> | ||||
| Networking sub component: | router | QA Contact: | Junqi Zhao <juzhao> | ||||
| Status: | CLOSED WONTFIX | Docs Contact: | |||||
| Severity: | low | ||||||
| Priority: | low | CC: | acomabon, alchan, aos-bugs, dmace, erich, fbranczy, fshaikh, jmalde, juzhao, rsandu, travi | ||||
| Version: | 3.11.0 | Keywords: | Reopened | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.11.z | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-11-04 22:01:38 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: | |||||||
| Attachments: |
|
||||||
If it's solved by opening the port on the firewall, this should be opened against the router team, not the monitoring team. Prometheus collects these metrics, but it's the router's responsibility to properly expose them. How was monitoring deployed? AFAIK router isn't integrated with the new (3.10) metrics stack yet. If this is a problem with the "openshift-prometheus" playbook, we're probably not going to fix it. (In reply to Dan Mace from comment #2) > How was monitoring deployed? AFAIK router isn't integrated with the new > (3.10) metrics stack yet. If this is a problem with the > "openshift-prometheus" playbook, we're probably not going to fix it. openshift_prometheus_state=present # Default node_selector is node-role.kubernetes.io/infra=true, you can change to other value openshift_prometheus_node_selector={'node-role.kubernetes.io/infra': 'true'} and run with playbook: playbooks/openshift-prometheus/config.yml If it's a firewall issue, then there is no need to be an issue for the monitoring component. It's an issue with the router setup, not monitoring/Prometheus. Closing this as a duplicate of 1552235. *** This bug has been marked as a duplicate of bug 1552235 *** Sorry, I accidentally marked my comment as private. Here it is in public: I'm afraid there are multiple related but separate conversations happening here. Router metrics aren't integrated out-of-the-box with Prometheus in 3.11, and as far as I know that's not going to change. This specific Bugzilla's report was a problem with access to a router metrics port through a firewall, and the workaround was apparently to manually open the firewall port. Any router Prometheus integration involved there was a DIY endeavor, because no such integration is supported in 3.11 out of the box. I'm going to close this bug. If there's still a lingering question about integrating routers with Prometheus out-of-the-box in 3.11's Prometheus playbook, I would recommend starting a discussion with PM outside BZ. |
Created attachment 1480982 [details] openshift-router target Description of problem: Deploy prometheus and access /targets page, router targets is down in prometheus targets UI. This because router port 1936 is not added to firewall, after adding, there is not such issue Version-Release number of selected component (if applicable): # rpm -qa | grep ansible openshift-ansible-roles-3.11.0-0.25.0.git.0.7497e69.el7.noarch ansible-2.6.3-1.el7ae.noarch openshift-ansible-docs-3.11.0-0.25.0.git.0.7497e69.el7.noarch openshift-ansible-playbooks-3.11.0-0.25.0.git.0.7497e69.el7.noarch openshift-ansible-3.11.0-0.25.0.git.0.7497e69.el7.noarch prometheus component images version: v3.11.0-0.25.0.0 How reproducible: Always Steps to Reproduce: 1. Deploy prometheus and access /targets page 2. 3. Actual results: router targets is down in prometheus targets UI Expected results: router targets should be up in prometheus targets UI Additional info: