virtualbox scripts do not support new interface names
Bug #1529794 reported by
Dmitry Bilunov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
High
|
Dmitry Bilunov | ||
8.0.x |
Won't Fix
|
High
|
Dmitry Bilunov | ||
Future |
Won't Fix
|
High
|
Dmitry Bilunov |
Bug Description
If the fuel master node is started without net.ifnames=0 (new interface names are enabled), then networking
scripts in fuel-main/
https:/
Related: #1496042
Changed in fuel: | |
status: | New → Confirmed |
milestone: | none → 9.0 |
importance: | Undecided → High |
milestone: | 9.0 → 8.0-updates |
tags: | added: area-build |
Changed in fuel: | |
milestone: | 8.0-updates → 9.0 |
status: | Confirmed → New |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: vbox-scripts |
Changed in fuel: | |
status: | Confirmed → Incomplete |
To post a comment you must log in.
Currently, I cannot test my patch, because fuel breaks in various ways (installer's initramfs does not complete; dockerctl build all fails; rabbitmq listens the wrong interface) if I force net.ifnames=1.