Bug 2162024

Summary: [Cinder] Multivalued options created with wrong syntax
Product: Red Hat OpenStack Reporter: Eric Nothen <enothen>
Component: puppet-cinderAssignee: Alan Bishop <abishop>
Status: CLOSED ERRATA QA Contact: Evelina Shames <eshames>
Severity: low Docs Contact: Andy Stillman <astillma>
Priority: medium    
Version: 17.0 (Wallaby)CC: abishop, jjoyce, jschluet, slinaber, tkajinam, tvignaud
Target Milestone: gaKeywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-cinder-18.5.2-1.20230127000858.6aa60e7.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:13:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Nothen 2023-01-18 15:59:27 UTC 
This bug was initially created as a copy of Bug #2042429

I am copying this bug because: 

The issue was resolved for:

- nova
- neutron
- keystone

But the same issue is still present in other services, such as:

- glance
- cinder
- octavia
- manila
- ceilometer
- heat
- designate
- barbican
- aodh
- ironic


Description of problem:
The notification_driver is a multivalued parameter, i.e. several drivers can be enabled, but the current code only enables the first string.

Given this code:

~~~
(admin@standalone) [stack@allinone170 ~]$ cat templates/notifications.yaml 
parameter_defaults:
  ExtraConfig:
    cinder::notification_driver:
      - "log"
      - "messagingv2"
~~~

The following is implemented:

~~~
[root@allinone170 ~]# egrep -v '^$|^#' /var/lib/config-data/cinder/etc/cinder/cinder.conf |grep -A1 oslo_messaging_notifications
[oslo_messaging_notifications]
driver=log
~~~
Comment 9 Lukas Svaty 2023-06-16 08:13:29 UTC 
Bulk moving target milestone to GA after the release of Beta on 14th June '23.
Comment 16 errata-xmlrpc 2023-08-16 01:13:15 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 (Release of components for Red Hat OpenStack Platform 17.1 (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-2023:4577