devstack initialization does not correctly initialize /etc/murano.conf

Bug #1435336 reported by Radek Pospisil
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Invalid
Undecided
Unassigned

Bug Description

[murano]/contrib/devstack/lib/murano initializes /etc/murano.conf with defaults, but

* some options are missing - e.g., 'login in section [rabbitmq]' is missing. Instead there is 'rabbit_userid in section [DEFAULT]'

* some options are generated in section [DEFAULT] which are deprecated (see log of murano-engine):
3 9278 WARNING oslo_config.cfg [-] Option "rabbit_userid" from group "DEFAULT" is deprecated. Use option "rabbit_userid" from group "oslo_messaging_rabbit".

It would be good to check/fix 'iniset' usages in [murano]/contrib/devstack/lib/murano

summary: - devstack initialization does not correctly initializes /etc/murano.conf
+ devstack initialization does not correctly initialize /etc/murano.conf
Changed in murano:
assignee: nobody → Alexey Deryugin (velovec)
milestone: none → kilo-rc1
Changed in murano:
status: New → Invalid
Revision history for this message
Radek Pospisil (radek-pospisil) wrote :

strange, I'm using Murano of last commit 7a08d3b81ff327379ef81fb350e887d599c4addd and I have to manually add "login=stackrabbit" to /etc/murano/murano.conf :

[rabbitmq]
password = noname
host = 16.60.142.48
login = stackrabbit <--- this line I have to add otherwise I've receive "[exceptions.IOError]: Socket closed" on environment deployment.

Why the 'login=stackrabbit' is not automatically added, if the similar conf line is added to the oslo_messaging_rabbit section ?
[oslo_messaging_rabbit]
rabbit_userid = stackrabbit
rabbit_password = noname
rabbit_hosts = 16.60.142.48

Changed in murano:
assignee: Alexey Deryugin (velovec) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.