Controllers ipv4 forwarding disabled when neutron and rabbitmq are decomposed
Bug #1682378 reported by
Lukasz Pelczyk
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
In Progress
|
High
|
Michael Polenchuk | ||
Bug Description
Fuel 9.2 - Control plane split into controllers, neutron nodes, and rabbitmq nodes.
Seems that all tasks which are setting ipv4 forwarding were delegated into decomposed nodes.
Controller left with:
root@node-107:~# cat /proc/sys/
0
When network templates being used, it causes a lot of troubles as namespaces are not working properly, thus almost all services are not able to communicate.
In my lab deployment (all nodes virtualized, no network templates, simple network) ip forwarding is disabled too, although everything is working fine.
Task graph should be reviewed and verified which task should be applied on controller to enable forwarding when neutron and rabbit are decomposed.
| Changed in fuel: | |
| assignee: | nobody → Michael Polenchuk (mpolenchuk) |
| milestone: | none → 12.0 |
| tags: | added: area-library |
| Changed in fuel: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Lukasz Pelczyk (lpelczyk) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-library (master) | #2 |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on fuel-library (master) | #3 |
To post a comment you must log in.
Workaround:
Add to deployment_
- id: fix_forwarding
type: shell
role: [controller, primary-controller, rabbitmq, primary-rabbitmq]
requires: [plugins_
required_for: [sync_time]
parameters:
cmd: sysctl -w net.ipv4.
retries: 3
interval: 20
timeout: 180