oslo-messaging-rpc with rabbitmq is broken with TLS everywhere
Bug #1771744 reported by
Juan Antonio Osorio Robles
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
High
|
Juan Antonio Osorio Robles | ||
Bug Description
Given that the new default for rabbitmq is using the OsloMessagingRpc resource, we now ended up with a broken TLS everywhere setup. This is due to the fact that the metadata info given in those services ir wrong. It points to oslo_messaging_rpc, while we never get a certificate for that principal.
| Changed in tripleo: | |
| status: | New → Incomplete |
| status: | Incomplete → Triaged |
| importance: | Undecided → High |
| milestone: | none → rocky-2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to tripleo-heat-templates (master) | #1 |
| Changed in tripleo: | |
| assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tripleo-heat-templates (master) | #2 |
| Changed in tripleo: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-heat-templates 9.0.0.0b3 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/