Description of problem:

having a system with a bond interface named, for example, bond-primary and then having a vlan interface over (bond-primary.101 for example) will break the registration.

Naming the interface bond0 (and the vlan bond0.101) works fine.

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

How reproducible:

Always
Steps to Reproduce:
1. Create a bond interface on a system. Name it bond-primary.
2. Create a vlan interface over the bond-primary interface. Call it bond-primary.101 (or whatever id you need)
3. Try registering the system on Satellite

Actual results:

1. subscription-manager register --org="DefaultOrganization" --activationkey="DefaultAK"
   Validation failed: Attached to can't be blank (HTTP error code 422: Unprocessable Entity)

Expected results:
Registration to happen without errors

Additional info:

Investigating the issue, I see that bond-primary (or anything on the format bond-<anything>) is not a match to the regex defined here: https://github.com/theforeman/foreman/blob/develop/app/services/fact_parser.rb#L5

If the interface name matches the regex defined there, then the registration works fine (I tested changing the regex to match the name).

I'm not sure about the reasoning for enforce a specific name format. I'd like to hear from engineering on it. Could we be more flexible on it?