Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJoniel Pasqualetto
2023-10-26 20:24:07 UTC
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
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?
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.