Bug 1327512
| Summary: | munin-limits not reporting actual state of variable to NSCA | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Tom Yates <madhatter> |
| Component: | munin | Assignee: | Kim B. Heino <b> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | el6 | CC: | b, drjohnson1, ingvar |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | munin-2.0.40-4.fc28 munin-2.0.40-4.fc29 munin-2.0.40-4.el6 munin-2.0.40-4.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-27 17:28:37 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
Tom Yates
2016-04-15 09:38:56 UTC
Have you filed this bug with upstream? https://github.com/munin-monitoring/munin/issues I haven't; I wasn't sure that the issue was in upstream, not the repackaging. I am happy to file with upstream if you can give me that assurance. Not least because the problem wasn't there in munin 2.0.25-2, and downgrading to those packages immediately fixed the problem. If I understand the numbering correctly, the differences there are entirely EPEL's - munin just releases 2.0.25. Not entirely accurate, 2.0.25-5 integrated the pre-2.0.26 patches that have not been released yet. They have not changed either, so the author was OK with a pre-release patch until he was ready to release 2.0.26. That makes sense (thank you!), but as far as I can tell from https://github.com/munin-monitoring/munin/releases 2.0.26 was never released, so I'm not entirely sure what I'm supposed to log with upstream. If anything, it seems to me like upstream are moving towards a 3.0 release (their dev release is *way* past 2.1, currently at 2.999.2). Perhaps epel should back out the 2.0.26-inspired changes, and hold fire until upstream release a new production version? OK, the problem is in upstream, I've just built 2.0.39 on CentOS 7 and I have the same problem. I have logged this with them at https://github.com/munin-monitoring/munin/issues/1052 . Upstream have produced a (three-line) patch which works for me with C6 and EPEL munin 2.0.33-1. Having restored EPEL munin to my (one and only) C7 server, I can confirm it works there, too. Interestingly, upstream say the regression was introduced in 2.0.26, which fits with the timing we see. Upstream patch at: https://github.com/munin-monitoring/munin/commit/f0fa843b34918a43e312777037c762d5638af275 It will be included in 2.0.41. munin-2.0.40-4.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-673f52b139 munin-2.0.40-4.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-6455129fce munin-2.0.40-4.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-39b27a8592 munin-2.0.40-4.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-bf0c049faf munin-2.0.40-4.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-673f52b139 munin-2.0.40-4.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-bf0c049faf munin-2.0.40-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-6455129fce munin-2.0.40-4.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-39b27a8592 munin-2.0.40-4.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. munin-2.0.40-4.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. munin-2.0.40-4.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. munin-2.0.40-4.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. |