Bug 2042429

Workaround for this issue using a NodeExtraConfigPost, as detailed on [1]


# 1. Environment file required for cadf, with multiple drivers for Keystone:

[stack.lab ~]$ cat templates/keystone.yaml 
parameter_defaults:
  NotificationDriver: "messagingv2"
  KeystoneNotificationTopics: "notifications"
  KeystoneRegion: TESTREGION
  KeystoneNotificationFormat: "cadf"
  ControllerExtraConfig:
    keystone::notification_driver:
      - "log"
      - "messagingv2"
    cinder::ceilometer::notification_driver: "log"
    glance::notify::rabbitmq::notification_driver: "log"
    heat::notification_driver: "log"
    neutron::notification_driver: "log"
    nova::notification_driver: "log"
    keystone::config::keystone_config:
      DEFAULT/notification_opt_out:
        value: "identity.authenticate.pending"


# 2. ConfigPost environment file:

[stack.lab ~]$ cat templates/overcloud-post.yaml 
resource_registry:
  OS::TripleO::NodeExtraConfigPost: /home/stack/post-deploy/keystone-driver-fix.yaml


# 3. Heat template that fixes keystone.conf:

[stack.lab ~]$ cat post-deploy/keystone-driver-fix.yaml 
heat_template_version: rocky

description: >
  Workaround to the [oslo_messaging_notifications]driver issue reported on BZ#2042429

parameters:
  servers:
    type: json
  DeployIdentifier:
    type: string
  EndpointMap:
    default: {}
    type: json

resources:
  CustomExtraConfig:
    type: OS::Heat::SoftwareConfig
    properties:
      group: script
      config: |
        #!/bin/bash
        set -x
        if [ -f /var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf ] ;then
            sed -i 's/\(^driver\)=\(.*\),\(.*\)$/\1=\2\n\1=\3/' /var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf && \
            systemctl restart tripleo_keystone.service
        fi

  CustomExtraDeployments:
    type: OS::Heat::SoftwareDeploymentGroup
    properties:
      servers:  {get_param: servers}
      config: {get_resource: CustomExtraConfig}
      actions: ['CREATE','UPDATE']
      input_values:
        deploy_identifier: {get_param: DeployIdentifier}

[stack.lab ~]$ 


[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/advanced_overcloud_customization/index#sect-Customizing_Overcloud_PostConfiguration_All

Hey, not urgent I know, but would it be possible to review this BZ and assign a target milestone, so that I can tell my customer on which Z stream to expect a fix?

wallaby backport: https://review.opendev.org/c/openstack/puppet-keystone/+/847439

verified:
[root@controller-0 ~]# rpm -qa| grep puppet-keystone-18.5.1-0.20220628111339.2606fdf.el9ost
puppet-keystone-18.5.1-0.20220628111339.2606fdf.el9ost.noarch

[root@controller-0 ~]# grep -A 15 'oslo_messaging_notifications' /var/lib/config-data/puppet-generated/keystone/etc/keystone/ -r
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf:[oslo_messaging_notifications]
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-#
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-# From oslo.messaging
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-#
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-# The Drivers(s) to handle sending notifications. Possible values are
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-# messaging, messagingv2, routing, log, test, noop (multi valued)
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-# Deprecated group/name - [DEFAULT]/notification_driver
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-#driver =
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-driver=log
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-driver=messagingv2
/var/lib/config-data/puppet-generated/keystone/etc/keystone/keystone.conf-

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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543