default route is left via eth0 but should via br-ex
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Stanislav Makar |
Bug Description
"build_id": "2015-03-
"ostf_sha": "1c7f799cb0e159
"build_number": "260",
"release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-03-
"auth_required": true,
"api": "1.0",
"nailgun_sha": "51ddbe0a2e379e
"production": "docker",
"python-
"astute_sha": "7292fc2a673cb1
"feature_groups": ["mirantis"],
"release": "6.1",
"fuelmain_sha": "178812b1971a90
"fuellib_sha": "27459a89cdac07
I reproduced this issue only for HA with 3 or more controllers
1. Create new environment (CentOS)
2. Choose nova-network, vlan
3. Add 4 controller, 2 compute, 3 cinder
4. Start deployment. It was successful
5. Start OSTF tests. Some of them failed because 'ping 8.8.8.8' doesn't wotk from controller and compute nodes
Controllers: node-13,14,15,16
Computes: node-17,18
[root@node-14 ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.169.254 - 255.255.255.255 !H 0 - 0 -
240.0.0.0 0.0.0.0 255.255.255.252 U 0 0 0 hapr-host
240.0.0.4 0.0.0.0 255.255.255.252 U 0 0 0 vrouter-host
10.20.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-fw-admin
10.20.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
172.16.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-storage
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 br-mgmt
0.0.0.0 10.20.0.2 0.0.0.0 UG 0 0 0 eth0
[root@node-14 ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2004ms
[root@node-14 ~]#
Logs are here: https:/
Changed in fuel: | |
importance: | Critical → High |
summary: |
- eth0 are located in routing, not in bridges + default route is left via eth0 but should via br-ex |
Changed in fuel: | |
status: | New → Confirmed |
It is weird - floating error :(
The access to this env was provided to me by reporter and I was looking for errors in log but nothing
Reseted this env and deployed again - all is fine