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.
Description of problem:
We have found hosts that contain a lot (thousands) of NICs on a single host.
From looking at the data, the nics were in form of:
{'ipv4_addresses': ['1.2.3.4'], 'ipv6_addresses': [], 'mtu': 1500, 'mac_address': '10:10:10:10:10:10', 'name': 'caliXXXXXXXXXXX'}
Those interfaces are created a lot with a random name and since Satellite accumulates all NIC crecords, the host record becomes bloated.
Apparently they are created by calico project (https://projectcalico.docs.tigera.io/reference/architecture/overview) and hence can be ignored.
How reproducible:
Always as long as you have calico generating them.
Steps to Reproduce:
1.Report about a host to Satellite server using either subscription-manager or puppet
2.Make sure the host generates a new interface each time
3.
Actual results:
A host record will contain too many nic records.
Expected results:
no cali* interfaces in the host record
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:8506
Description of problem: We have found hosts that contain a lot (thousands) of NICs on a single host. From looking at the data, the nics were in form of: {'ipv4_addresses': ['1.2.3.4'], 'ipv6_addresses': [], 'mtu': 1500, 'mac_address': '10:10:10:10:10:10', 'name': 'caliXXXXXXXXXXX'} Those interfaces are created a lot with a random name and since Satellite accumulates all NIC crecords, the host record becomes bloated. Apparently they are created by calico project (https://projectcalico.docs.tigera.io/reference/architecture/overview) and hence can be ignored. How reproducible: Always as long as you have calico generating them. Steps to Reproduce: 1.Report about a host to Satellite server using either subscription-manager or puppet 2.Make sure the host generates a new interface each time 3. Actual results: A host record will contain too many nic records. Expected results: no cali* interfaces in the host record Additional info: