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.

Created attachment 1363599 [details]
Registration log

Description of problem:
Long registration time of docker host with 100 network interfaces

Version-Release number of selected component (if applicable):
Satellite 6.2.12 with bugzilla 1483677 hotfix already applied

How reproducible:
subscription-manager register of a docker host with many network interfaces

Steps to Reproduce:
1.
2.
3.

Actual results:
longer than 60 seconds

Expected results:
Few seconds at most

Additional info:

Created attachment 1363601 [details]
dynflow steps and times

This feature was released with Satellite 6.3. If you are still seeing issues, please feel free to re-open with additional information.