Red Hat Bugzilla – Bug 1304860
sensu pkg in rhel-7-server-openstack-7.0-optools-rpms is too old (0.16.0) please update to 0.2x
Last modified: 2016-04-07 16:24:38 EDT
* Description of problem:
rhel-7-server-openstack-7.0-optools-rpms provides this rpm:
The current upstream version of 'sensu' is a lot more recent (0.22.0 at time of this writing).
I had been testing 0.20.6 from the sensu yum repos (http://repositories.sensuapp.org/yum/7/x86_64/) and it worked quite better for the following reasons:
1) the client nodes were faster to reconnect/reconfigure to the sensu server.
2) the server was faster to absorb the check results of its clients when absorbing a large number of new clients.
3) when rebooting the sensu server, the 0.16.0 rpm required some manual LTC (as in systemctl restart <svc1> <svc2>) whereas 0.20.6 did not (all services came back online sucessfully).
4) The upstream patch to display the output from the 'GREEN' checks works on 0.20.6, not on 0.16.0 (the green checks show -no- output at all).
Upstream patch: https://github.com/sensu/uchiwa/issues/404
Applying the above patch to uchiwa-0.8.1-2.el7ost.x86_64.rpm works if sensu is 0.20.6 but not if sensu is the 0.16.0 from the CDN repos.
Version-Release number of selected component (if applicable):
Please consider rebasing to 0.20.6 or above.
Created attachment 1121454 [details]
sensu01 client details with sensu 0.16.0 from CDN
Created attachment 1121455 [details]
sensu01 client details with sensu 0.20.6 from CDN
Look at the differences between the two screenshots..
With 0.16.0 + upstream patch (https://github.com/sensu/uchiwa/issues/404), there are no outputs displayed when the checks are green.
with 0.20.6 + upstream patch (since I'm using the uchiwa from CDN), tons of information are displayed.
It would be great if we could get this output with a version of sensu/uchiwa from CDN..
Thank you! :)
We can look at this for Operational Tools for OSP 8.
I've noticed 0.22.0 in the repos.. Would you consider using 0.22.1 instead? It just came out..
*** Bug 1320140 has been marked as a duplicate of this bug. ***
We can look at rebasing again later, if needed.
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.