The default gateway isn't properly configured for the nodes with LMA roles
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StackLight |
Fix Released
|
Medium
|
Simon Pasquier |
Bug Description
Tested with MOS8 and 0.9.0 plugins.
The default gateway for the nodes with elasticsearch_
LMA node:
ip r
default via 172.16.160.1 dev br-fw-admin
unreachable 169.254.169.254 scope host
172.16.160.0/24 dev br-fw-admin proto kernel scope link src 172.16.160.29
192.168.0.0/24 dev br-mgmt proto kernel scope link src 192.168.0.11
192.168.1.0/24 dev br-storage proto kernel scope link src 192.168.1.6
192.168.2.0/24 dev br-mesh proto kernel scope link src 192.168.2.7
240.0.0.0/30 dev hapr-host proto kernel scope link src 240.0.0.1
Compute node:
# ip r
default via 192.168.0.1 dev br-mgmt
unreachable 169.254.169.254 scope host
172.16.160.0/24 dev br-fw-admin proto kernel scope link src 172.16.160.25
192.168.0.0/24 dev br-mgmt proto kernel scope link src 192.168.0.10
192.168.1.0/24 dev br-storage proto kernel scope link src 192.168.1.7
192.168.2.0/24 dev br-mesh proto kernel scope link src 192.168.2.4
This is because the plugins don't call the configure_
Note that this doesn't apply to the dedicated environments (when no controller is deployed).
Related bug: https:/
Changed in lma-toolchain: | |
milestone: | 0.10.0 → none |
Changed in lma-toolchain: | |
milestone: | none → 0.10.1 |
Changed in lma-toolchain: | |
milestone: | 0.10.1 → 0.11.0 |
Changed in lma-toolchain: | |
milestone: | 0.11.0 → 1.0.0 |
Changed in lma-toolchain: | |
status: | Fix Committed → Fix Released |
See also https:/ /bugs.launchpad .net/fuel- plugins/ +bug/1591117