[library] fixing notifications.info rabbitmq when adding in a second external network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Library (Deprecated) | ||
4.1.x |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) |
Bug Description
After completing a FUEL 4.1 openstack deployment using multi--node (NO HA) I needed to add in an 2nd external network.
Everything functionally worked - but I got the following error in /var/log/rabbitmq:
channel 1 - error: {amqp_error,
To fix this on my fuel server I edited the file: /etc/puppet/
I edited line 77 to: 'DEFAULT/
After this I deployed my openstack environment and went ahead and added in my second network. This seemed to fix my problem.
This is certainly not the correct fix, but it highlights the issue I encountered.
You may not consider this an real FUEL bug since I went ahead an modified my openstack environment post FUEL deployment.
But I thought I would report my issue.
Changed in fuel: | |
milestone: | none → 4.1.1 |
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
importance: | Undecided → Medium |
Changed in fuel: | |
milestone: | 4.1.1 → 5.0.1 |
no longer affects: | fuel/5.1.x |
summary: |
- fixing notifications.info rabbitmq when adding in a second external - network + [library] fixing notifications.info rabbitmq when adding in a second + external network |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
status: | Triaged → Won't Fix |
status: | Won't Fix → Invalid |
AFAIK, rabbit_ha_queues should never be used for non HA multinode.