Murano does not support SSL with cert for engine<>agent communication
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
High
|
Konstantin | ||
Kilo |
Won't Fix
|
Undecided
|
Unassigned | ||
Liberty |
New
|
Undecided
|
Unassigned | ||
Mitaka |
Fix Committed
|
High
|
Konstantin | ||
Newton |
Fix Released
|
High
|
Konstantin |
Bug Description
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/
[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:
Update core-library, example for stable/kilo - https:/
Impact:
Murano does not work on any environment which requires certificates used for SSL connectivity
tags: | added: kilo-backport-potential liberty-backport-potential mitaka-backport-potential |
tags: | added: in-stable-mitaka |
Fix proposed to branch: master /review. openstack. org/307349
Review: https:/