[murano] notification_driver=messagingv2 is not set in config file

[Ekaterina Chernova]

Deployment hangs up in stage of Agent task execution
The reson is notification_driver=messagingv2 is not set in /etc/murano/murano.conf

[Dmitry Borodaenko (angdraug)]

Why is it Fix Committed? Which commit has fixed it?

[Igor Yozhikov (iyozhikov)]

6.0 - https://review.openstack.org/#/c/129660/
5.1 - https://review.openstack.org/#/c/129660/
5.0 - https://review.openstack.org/#/c/131385/

[Alexander Tivelkov (ativelkov)]

Strangely, this seems to be still an issue in ISO #110 of MOS 9.0

[Dina Belova (dbelova)]

Denis, please take a look on #110 ISO 9.0 due to Alex's comments.

[Kirill Zaitsev (kzaitsev)]

Please take note, that might be happening, because the parameter has been moved to a different group in newer versions of oslo.messaging

https://github.com/openstack/oslo.messaging/commit/33c1010c3281804456a22b769c4bac5ac6a7cca1#diff-570e2755c497a2648f3c9512602327e5

apparently this happened in the version 3.1.0 of oslo.messaging, if I'm reading that link correctly.

[Kirill Zaitsev (kzaitsev)]

My comment doesn't seem relevant as MOS 9.0 seems to have http://perestroika-repo-tst.infra.mirantis.net/mos-repos/ubuntu/9.0/pool/main/o/oslo.messaging/ seems to have 1.8.3 version of oslo.messaging

[Kirill Zaitsev (kzaitsev)]

ok, another update — http://mirror.fuel-infra.org/mos-repos/ubuntu/master/pool/main/p/python-oslo.messaging/ the actual mirror of mos repos. 4.5.0 is the version, so I might be right about my comment. Need to set it in a different group

[Denis Egorenko (degorenko)]

https://review.openstack.org/#/c/298658/

[Ivan Berezovskiy (iberezovskiy)]

Fix is merged

[Alex Kholkin (akholkin)]

Verified on #289 ISO
MOS 9.0