Detailed bug description:
Murano does support specifying certificate for SSL connectivity between murano-engine and murano-agent, but this value (along side with certificate) is not passed to the murano-agent during first VM boot through cloud-init.
Steps to reproduce:
1. Configure SSL for Murano RabbitMQ
2. Configure SSL in Murano:
vi /etc/murano/murano.conf
[rabbitmq]
...
ssl=True
ca_certs=<path-to-cert>
3. Deploy any application
Expected results:
Environment with application deployed successfully
Actual result:
Environment with application hangs during deployment, murano-agent configuration of VM does not anything related to cert configured
Detailed bug description:
Murano does support specifying certificate for SSL connectivity between murano-engine and murano-agent, but this value (along side with certificate) is not passed to the murano-agent during first VM boot through cloud-init.
Steps to reproduce: murano. conf certs=< path-to- cert>
1. Configure SSL for Murano RabbitMQ
2. Configure SSL in Murano:
vi /etc/murano/
[rabbitmq]
...
ssl=True
ca_
3. Deploy any application
Expected results:
Environment with application deployed successfully
Actual result:
Environment with application hangs during deployment, murano-agent configuration of VM does not anything related to cert configured
Reproducibility:
Always
Workaround: /review. openstack. org/301365
Update core-library, example for stable/kilo - https:/
Impact:
Murano does not work on any environment which requires certificates used for SSL connectivity