Bug 1476651 - Primary interface is not recognized when VLAN id is entered
Summary: Primary interface is not recognized when VLAN id is entered
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Image
Version: 6.2.10
Hardware: x86_64
OS: Linux
Target Milestone: 6.6.0
Assignee: Lukas Zapletal
QA Contact: Jitendra Yejare
Depends On:
TreeView+ depends on / blocked
Reported: 2017-07-31 03:37 UTC by jalviso
Modified: 2023-03-24 13:50 UTC (History)
10 users (show)

Fixed In Version: foreman-1.22.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-22 19:57:02 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24711 0 Normal Closed Virtual interfaces are not detected as primary (discovery over VLAN support) 2021-02-01 02:27:44 UTC

Comment 4 Lukas Zapletal 2017-09-21 12:30:21 UTC

Using the VLANID feature to use VLAN Tag during discovery and trying FDI image 6.2 and latest 6.4.0 failed to PXE-less provisioned a physical system, 

As per facts shown in production.log, discovery_bootif is picking up UUID of a non-active interface, not the primary interface set in VLAN:


From discovery-debug:

NAME                         UUID                                  TYPE            DEVICE
primary                      45c4fdee-4c10-11e7-a233-40f2e9c2b808  vlan            eno1.463
secondary-40:f2:e9:xx:xx:xx  45d04ece-4c10-11e7-a53b-40f2e9c2b808  802-3-ethernet  --
secondary-40:f2:e9:xx:xx:xx  eb204704-4c0f-11e7-b727-40f2e9c2b808  802-3-ethernet  --

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:

1- Boot the server from the foreman discovery iso v 3.4 downloaded upstream "http://downloads.theforeman.org/discovery/releases/3.4/"

2- Select Manual Discovery

3- Select the interface , and in the same window at the bottom you can find the VLAN ID

4- Enter the IP/MASK/GATEWAY and DNS servers 

5- Hit next, then the tool configures new interface with name <interface.vlanid> (example enp0s8.463) and moves to the next screen

At this point the interface is up and pingable on the network 

6- Enter the Satellite server IP:PORT and Proxy setting and selecting proxy. 

7- No custom facts configured, hitting next 

Actual results:

Server discovery returns with error:

ERROR -- : Discovery failed, code 422, reason: ERF42-1064 [Foreman::Exception]: Unable to assign subnet, primary interface is missing IP address 

Expected results:

PXE-less provision succeeds using the VLAN configured Primary interface.

Additional info:

Can ssh to the Host via the interface that is configured with the IP address which means it is routable back to the Server.

Comment 5 Lukas Zapletal 2017-09-21 12:36:22 UTC

On the last Custom page screen, enter the primary interface mac address:

Fact name:

Fact value:

This should override the facts reported.


In Satellite6 select different fact that could hold primary interface, this could be "macaddress". This could also work. In Satellite6 in Administer - Setting set "Interface fact" to "macaddress" (it is "discovery_bootif" by default).

Alternatively, when using same network cards on all systems, this can be set to "macaddress_enp0s8.463" which will contain the correct MAC address, but this will only work for subset of hosts.

Comment 11 Lukas Zapletal 2018-01-09 14:15:44 UTC
Okay, there are two problems, both stems from the fact that when VLAN is set up, both eth0 and eth0.VLANID interfaces have same MAC address:

A) Discovery primary NIC detection does not priorize NIC with IP, since eth0 comes first it detects wrong one without IP. Easy fix, one liner.


B) NIC importer in Foreman core does not properly handle situation when two interfaces have same MAC address. This is more complex issue that needs further investigation.


Comment 16 Lukas Zapletal 2018-11-23 14:07:02 UTC
Thanks, this is a long-standing problem, discovery provisioning over VLAN hasn't been tested with Satellite 6. We are working hard on this but unsure when the fix lands in Satellite.

There is currently no workaround possible, unfortunately the only option is not to use tagged VLAN for node discovery. Simple PXE workflow does work however with some template changes (vlanid for Anaconda), we are also aiming shipping these changes in standard templates in near future.

In both cases, provisioning on VLAN tagged networks is listed in unsupported (untested) scenarios until we finish this.


Comment 21 Bryan Kearney 2019-01-29 13:06:50 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24711 has been resolved.

Comment 31 Bryan Kearney 2019-10-22 19:57:02 UTC
This was delivered in Satellite 6.6.

Note You need to log in before you can comment on or make changes to this bug.