Bug #38870
closed
Can't register systems with bond interface named bond-<something> AND a tagged vlan on the same interface
Description
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:
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
Updated by The Foreman Bot 9 months ago
- Status changed from Need more information to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/10744 added
Updated by Chris Roberts 9 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|693ba75003abca37e7d672ea7b75d5c0c83eef29.
Updated by Gerald Vogt 4 months ago
This breaks the correct typing of a primary interface with name bond0.601 from Nic::Managed to Nic::Bond.
See https://community.theforeman.org/t/foreman-3-17-2-messed-up-interface-facts/46101