Comment 1 for bug 1156844

This problem can happen in a multi-nic scenarios when using injected network template.

In nova.api.metadata.base.InstanceMetadata, when fetching network information with network.API().get_instance_nw_info, the initial network order is lost as the list of network ports returned by Quantum is sorted by port_id.

The injected network template is then erroneous and the instance will not be able to correctly configure its network interfaces.

get_instance_nw_info accepts a networks parameter which can be used to "ensure ports are in preferred network order". Unfortunately, it seems nova.api.metadata.base.InstanceMetadata does not have such information at that time.

Should anyone have an idea on how to fix it, it would be much appreciated.