Description of problem: From last openstack-tripleo-heat-templates NotificationDriver default value is set to messagingv2, for example for usr/share/openstack-tripleo-heat-templates/deployment/neutron/neutron-base.yaml ~~~ NotificationDriver: type: string default: 'messagingv2' description: Driver or drivers to handle sending notifications. ~~~ it's the same for most of the base yaml services. I expected this value should be noop as upstream code[2] Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-11.3.2-1.20210408163453.el8ost.noarch.rpm and previous. Actual results: Deploy of a new env can bring NotificationDriver to messagingv2 in openstack services that make notification to rabbitmq that no one consume without telemetry service enabled Expected results: NotificationDriver to noop Additional info: [1] https://access.redhat.com/downloads/content/rhel---8/x86_64/9895/openstack-tripleo-heat-templates/11.3.2-1.20210408163453.el8ost/noarch/fd431d51/package [2] https://github.com/openstack/tripleo-heat-templates/blob/stable/train/deployment/neutron/neutron-base.yaml
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 16.1.7 (Train) bug fix and 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/RHBA-2021:3762