Public network is assigned to random interface on virtualbox installation
Bug #1261718 reported by
Dmitry Pyzhov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Aleksey Kasatkin |
Bug Description
On some clusters public network is on eth1 interface, on some clusters is on eth2.
Expected behavior: on virtualbox installation it always must be on the same interface, for example eth1. Installation should have internet access.
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Aleksey Kasatkin (alekseyk-ru) |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Are you sure it is random?
For me I believe it is always same for Neutron VLAN mode (see screenshot) - where public net is on eth1.
I would expect it to be on eth2, because of the following default config in vbox scripts: UP,BROADCAST, RUNNING, SIMPLEX, MULTICAST> mtu 1500 UP,BROADCAST, RUNNING, SIMPLEX, MULTICAST> mtu 1500 UP,BROADCAST, RUNNING, SIMPLEX, MULTICAST> mtu 1500
vboxnet0: flags=8843<
ether 0a:00:27:00:00:00
inet 10.20.0.1 netmask 0xffffff00 broadcast 10.20.0.255
vboxnet1: flags=8843<
ether 0a:00:27:00:00:01
inet 172.16.1.1 netmask 0xffffff00 broadcast 172.16.1.255
vboxnet2: flags=8843<
ether 0a:00:27:00:00:02
inet 172.16.0.1 netmask 0xffffff00 broadcast 172.16.0.255
and 172.16.0.0/24 subnet used for public range, so after deployment I can login to Horizon via public network.
Unfortunately it is not the case at the moment.