Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1549167 - Sensu major update to 1.1.3
Sensu major update to 1.1.3
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: sensu (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
high Severity urgent
: beta
: 13.0 (Queens)
Assigned To: Martin Magr
Leonid Natapov
: Rebase, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-26 10:15 EST by Martin Magr
Modified: 2018-06-27 09:09 EDT (History)
10 users (show)

See Also:
Fixed In Version: sensu-1.1.3-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-06-27 09:08:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2084 None None None 2018-06-27 09:09 EDT

  None (edit)
Description Martin Magr 2018-02-26 10:15:54 EST
Description of problem:
We need to include following updates (or new builds) of packages for OSP13 to have Sensu client version 1.1.3 in the release

sensu-1.1.3-2.el7ost
rubygem-eventmachine-1.2.5-1.el7ost
rubygem-sensu-extensions-1.9.0-1.el7ost
rubygem-sensu-extensions-check-dependencies-1.0.1-1.el7ost
rubygem-sensu-extensions-occurrences-1.2.0-1.el7ost
rubygem-sensu-json-2.1.0-1.el7ost
rubygem-oj-2.18.1-1.el7ost
rubygem-sensu-redis-2.2.0-1.el7ost
rubygem-sensu-settings-10.9.0-1.el7ost
rubygem-parse-cron-0.1.4-1.el7ost

Other Sensu dependencies were not updated and should be included from OSP12 release.
Comment 5 Leonid Natapov 2018-05-09 04:25:31 EDT
Verified. all the described packages are included in the puddle from 2018-05-04.1
Basic sanity done.
Comment 7 errata-xmlrpc 2018-06-27 09:08:58 EDT
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/RHEA-2018:2084

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