virtualbox scripts do not support new interface names

Bug #1529794 reported by Dmitry Bilunov
6
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/virtualbox would fail. There are plenty of references to ethN, which would fail in this case.

https://review.openstack.org/258568

Related: #1496042

Revision history for this message
Dmitry Bilunov (dbilunov) wrote :

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.

Changed in fuel:
assignee: nobody → Dmitry Bilunov (dbilunov)
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
Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :

Actually - you should not run master with manual option 'net.ifnames=0'
fuel master automatically handle renaming to ifnames schema -
https://github.com/openstack/fuel-main/blob/master/iso/bootstrap_admin_node.sh#L63
From my pov - vbox scripts should be updater to new schema.

Revision history for this message
Dmitry Bilunov (dbilunov) wrote :

Could you provide a build version with definitely works with a new ifnames schema so I could try out new vbox scripts?

Changed in fuel:
status: Confirmed → Incomplete
Revision history for this message
Dmitry Bilunov (dbilunov) wrote :

If doesn't look like we have plans to make everything work using new interface naming scheme in near future.

Changed in fuel:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.