Bug 1933197 - sensubility refuses to connect to Sensu server
Summary: sensubility refuses to connect to Sensu server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: collectd-sensubility
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z1
: 16.2 (Train on RHEL 8.4)
Assignee: Martin Magr
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-25 22:14 UTC by Martin Magr
Modified: 2021-09-15 07:12 UTC (History)
3 users (show)

Fixed In Version: collectd-sensubility-0.1.8-2.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-15 07:12:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github infrawatch apputils pull 10 0 None closed Don't fail on missing sensu subscription 2021-02-25 22:17:00 UTC
Red Hat Product Errata RHEA-2021:3483 0 None None None 2021-09-15 07:12:58 UTC

Description Martin Magr 2021-02-25 22:14:54 UTC 
Description of problem:
If there are no checks on all openstack-* subscription channels the sensubility refuses to connect to the server.

[ERROR] Failed to spawn RabbitMQ connector. [connection: amqp://sensu:secret.24.1:5672//sensu, error: Exception (404) Reason: "NOT_FOUND - no exchange 'overcloud-cinder-api' in vhost '/sensu'"

We need to enable connection just to those channels which exists and fail only if there is no channel to connect to.
Comment 10 errata-xmlrpc 2021-09-15 07:12:30 UTC 
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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-2021:3483
Note You need to log in before you can comment on or make changes to this bug.