Enabling SSL on rabbitmq breaks pacemaker resource check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
In Progress
|
Undecided
|
Felipe Reyes | ||
OpenStack HA Cluster Charm |
Fix Released
|
Undecided
|
Felipe Reyes | ||
OpenStack Nova Cloud Controller Charm |
In Progress
|
Undecided
|
Felipe Reyes |
Bug Description
- Deployed Ocata with Juju 2.3.3
nova-cloud-
rabbitmq-server 3.5.7 active 3 rabbitmq-server jujucharms 239 ubuntu
- Once rabbitmq is configured with SSL
juju config rabbitmq-server ssl=on
- CRM reports nova_consoleauth resource start failure
root@juju-
[snippet]
Failed Actions:
* res_nova_
last-rc-change='Thu Mar 1 16:42:29 2018', queued=0ms, exec=20003ms
* res_nova_
last-rc-change='Thu Mar 1 16:42:49 2018', queued=0ms, exec=20002ms
[/snippet]
- That's due to default rabbitmq port (TCP 5672) used by pacemaker to check if nova_consoleauth has successfully connected to rabbitmq server
https:/
- When rabbitmq is configured with SSL the port number will change to TCP 5671
- Workaround is to update crm resource with valid port number
crm_resource --resource res_nova_
- Nova cloud controller charm should automatically update default rabbitmq port depended if SSL is enabled or not
tags: | added: sts |
Changed in charm-nova-cloud-controller: | |
assignee: | nobody → Felipe Reyes (freyes) |
Changed in charm-hacluster: | |
milestone: | none → 19.04 |
Changed in charm-hacluster: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/573824
Review: https:/