neutron should not try to bind port on compute with hypervisor_type ironic

[Vasyl Saienko]

Neutron tries to bind port on compute where instance is launched. It doesn't make sense when hypervisor_type is ironic, since VM does not live on hypervisor in this case. Furthermore it leads to failed provisioning of baremetal node, when neutron is not configured on ironic compute node.

Setup:
node-1: controller
node-2: ironic-compute without neutron

neutron-server.log: http://paste.openstack.org/show/445388/

[Ashok kumaran B (ashokkumaran-b)]

I can reproduce this defect, can someone have a look please?

[Chuck Carlino (ccarlino)]

Neutron ports of ironic servers have always had vif_type == VIF_TYPE_BINDING_FAILED. What was changed (in kilo I think) is that neutron now logs an error for all bind failures. IMO, the neutron work here is to avoid logging the errors in this case.

Also, https://blueprints.launchpad.net/ironic/+spec/ironic-ml2-integration may affect this.

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Trinath Somanchi (trinath-somanchi)]

This bug description is incomplete. kindly add the required info stated by BUGCHECKER.

[Sam Betts (sambetts)]

I think the best solution for this would be to use the right vnic type for baremetal and have an ml2 driver to handle marking statically configured baremetal connections as bound.

https://review.openstack.org/#/c/339129/8

[Kevin Benton (kevinbenton)]

+1 to @Sam's suggestion. Neutron is responsible for binding all ports, including Ironic ones. Add an ML2 driver to bind your ports.