Bug 1486191 - keystone should not be configured with amqp notifications without telemetry
Summary: keystone should not be configured with amqp notifications without telemetry
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: zstream
: 12.0 (Pike)
Assignee: Harry Rybacki
QA Contact: Pavan
URL:
Whiteboard:
Depends On: 1542537
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-29 07:53 UTC by Attila Fazekas
Modified: 2018-06-11 10:35 UTC (History)
7 users (show)

Fixed In Version: instack-undercloud-7.4.9-2.el7ost, openstack-tripleo-heat-templates-7.0.9-7.el7ost, puppet-tripleo-7.4.8-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-11 10:35:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1729293 0 None None None 2017-11-01 12:11:20 UTC
OpenStack gerrit 516969 0 None None None 2017-11-01 12:12:17 UTC
OpenStack gerrit 516979 0 None None None 2017-11-01 12:56:27 UTC
OpenStack gerrit 516982 0 None None None 2017-11-01 12:56:42 UTC
OpenStack gerrit 516989 0 None None None 2017-11-01 13:17:12 UTC

Description Attila Fazekas 2017-08-29 07:53:17 UTC 
Description of problem:

The keystone is configured to send notification to the telemetry service,
but the undercloud does not have telemetry service, so it just consumes the rabbitmq's memory. 

keystone.conf:
[oslo_messaging_notifications]
driver=messaging
topics=notifications
[oslo_messaging_rabbit]
rabbit_host=192.168.24.1
rabbit_userid=4547803a323cc8f377daee7602aa93d3d03d53f8
rabbit_password=dae5ceedfffb452ad5ebf504e209090c6f4de8f4

Version-Release number of selected component (if applicable):
instack-undercloud-7.2.1-0.20170729010706.el7ost.noarch
openstack-tripleo-validations-7.2.1-0.20170807182119.1f60b6f.el7ost.noarch
openstack-tripleo-puppet-elements-7.0.0-0.20170803140906.4e7d35d.el7ost.noarch
openstack-tripleo-ui-7.2.1-0.20170805065336.ac9467f.el7ost.noarch
puppet-tripleo-7.2.1-0.20170807233007.4600842.el7ost.noarch
openstack-tripleo-common-7.4.1-0.20170807001945.8c46306.el7ost.noarch
python-tripleoclient-7.2.1-0.20170807222309.a731597.el7ost.noarch
openstack-tripleo-common-containers-7.4.1-0.20170807001945.8c46306.el7ost.noarch
openstack-tripleo-heat-templates-7.0.0-0.20170805163048.el7ost.noarch
openstack-tripleo-image-elements-7.0.0-0.20170725091025.f3f06c7.el7ost.noarch
Comment 3 Harry Rybacki 2018-01-30 16:23:56 UTC 
Moving this bug to post as upstream reviews have all merged and LP#1729293 shows fix-released. Will determine if change slipped into a zstream release at some point and update bug accordingly.
Comment 4 Lon Hohberger 2018-03-29 10:34:37 UTC 
According to our records, this should be resolved by instack-undercloud-7.4.9-2.el7ost.  This build is available now.
Comment 5 Lon Hohberger 2018-03-29 10:34:42 UTC 
According to our records, this should be resolved by openstack-tripleo-heat-templates-7.0.9-8.el7ost.  This build is available now.
Comment 6 Lon Hohberger 2018-03-29 10:34:50 UTC 
According to our records, this should be resolved by puppet-tripleo-7.4.8-5.el7ost.  This build is available now.
Note You need to log in before you can comment on or make changes to this bug.