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
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.