expecting metadata server is reachable on the lexical first interface

This bug was originally filed in Launchpad as [LP: #1813812](https://bugs.launchpad.net/cloud-init/+bug/1813812)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2019-01-29T17:44:24.003895+00:00

date_fix_committed = None

date_fix_released = None

id = 1813812

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1813812

milestone = None

owner = rjschwei

owner_name = Robert Schweikert

private = False

status = triaged

submitter = rjschwei

submitter_name = Robert Schweikert

tags = ['sts']

duplicates = []

_Launchpad user **Robert Schweikert(rjschwei)** wrote on 2019-01-29T17:44:24.003895+00:00_

In OpenStack it is possible to configure a network setup such that the metadata server is accessible via a "secondary" NIC, for example eth1. In such a setup cloud-init fails to locate the proper NIC to access the metadata server.

No source files or tests are identified in the issue. Start by reproducing the OpenStack setup where the metadata server is reachable through a secondary NIC such as eth1, then trace how cloud-init selects the interface; the issue is done when metadata discovery succeeds through that interface.

Written by the indexing model from the issue text.