Bug 1744549
Summary: | cephmetrics-ansible only opens port 9283 on first mgr | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Torben Hørup <torben> |
Component: | Ceph-Metrics | Assignee: | Boris Ranto <branto> |
Status: | CLOSED ERRATA | QA Contact: | Uday kurundwade <ukurundw> |
Severity: | high | Docs Contact: | Erin Donnelly <edonnell> |
Priority: | high | ||
Version: | 3.3 | CC: | branto, ceph-eng-bugs, edonnell, flucifre, gmeno, pcuzner, tchandra, tserlin, ukurundw, zcerza |
Target Milestone: | z1 | ||
Target Release: | 3.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cephmetrics-2.0.7-1.el7cp | Doc Type: | Bug Fix |
Doc Text: |
.The Prometheus exporter port is now opened on all `ceph-mgr` nodes
Previously, the `ceph-mgr` playbook was not run on each `ceph-mgr` node, which meant the `ceph-mgr` Prometheus exporter port was not being opened on each node. With this update, the `ceph-mgr` playbook runs on all the `ceph-mgr` nodes, and the Prometheus exporter port is opened on all `ceph-mgr` nodes.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-22 13:29:24 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1726135 |
Description
Torben Hørup
2019-08-22 12:06:16 UTC
Workaround: ansible -i hosts.ini mgrs -m shell -a "firewall-cmd --add-port 9283/tcp" -become ansible -i hosts.ini mgrs -m shell -a "firewall-cmd --permanent --add-port 9283/tcp" -become Agree that this is an oversight! Looking at the git history, this has been the case for a while. Currently discussing the best option for fixing the issue. PM priority for first Z. 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, 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/RHBA-2019:3173 |