can't disable file injection for bare metal
Bug #1178103 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Invalid
|
High
|
Unassigned | ||
OpenStack Compute (nova) |
Fix Released
|
High
|
Joe Gordon | ||
tripleo |
Fix Released
|
High
|
Joe Gordon |
Bug Description
For two reasons : a) until we have quantum-pxe done, it won't work, and b) file injection always happens.
One of the reasons to want to disable file injection is to work with hardware that gets a ethernet interface other than 'eth0' - e.g. if only eth1 is plugged in on the hardware, file injection with it's hardcoded parameters interferes with network bringup.
A workaround for homogeneous environments is to change the template to hardcode the interface name (s/iface.
description: | updated |
description: | updated |
Changed in ironic: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | none → icehouse-1 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
Marking as wishlist because 1) it's not something which *can* be fixed now, 2) supporting file injection isn't broken per-se. Making it optional would clearly be an improvement, though.