876a9d4027
When using drivers like `networking-generic-switch`, there can be issues with changing the VLAN the server is attached to. Currently, the instance will still continue to attempt to boot, in some cases the instance can go into ACTIVE (if the server happens to be on the provisioning network already), but the server is not attached to the correct VLAN, generally causing the network to fail to come up. If we look at the ports, they are marked as binding failed. This is something that Nova checks for after doing the port update to attach the binding information. Lets add that check into Ironic, such that the above build will fail with a good hint at where to look for problems (namely Neutron). Change-Id: I3811941a3dff0a9f968258d05cc020e1f52e3e40
11 lines
500 B
YAML
11 lines
500 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds a new boolean configuration option ``[neutron]fail_on_port_binding_failure``
|
|
and corresponding node ``driver_info`` setting ``fail_on_binding_failure``
|
|
to control whether deployment should fail or continue if Neutron port
|
|
binding fails. With a default of ``true``, if your network is not
|
|
configured properly, this will likely cause deployment failures.
|
|
To maintain the previous behavior, explicitly set this option to False in
|
|
your configuration.
|