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.
Hosts like hypervisors or docker hosts may often change interfaces (e.g. network bridges) which confuses Foreman and during fact import it creates more and more interfaces, old are never deleted. After some time when a host passes thousands of interfaces, due to O(n^2) one fact upload can take several minutes of processing.
We need to delete old interfaces from Foreman database, either during fact upload directly or on schedule (those that hasn't been updated for a while).
The behvior is really bad, Foreman eats up all memory until passenger process is restarted, which can take a while (non-Enterprise version do not have maximum memory setting).
Verification steps:
1. register a host with multiple network interfaces
2. ensure the interfaces are loaded when going to the host details, and that the interfaces are not marked as managed
3. Go to Administer -> Settings -> Provisioning, add a pattern that would match one of the interfaces "Ignore interfaces with matching identifier"
4. foreman-rake interfaces:clean
5. the interfaces that match the pattern should be removed from the host
Created attachment 1485789[details]
One interface removed
Followed inecas' instruction.
1. Registered a host with multiple network interfaces
2. Saw that interfaces are not marked as managed. (eth1)
3. Added eth1 to the "Ignore interfaces with matching identifier" list
4. Ran foreman-rake interface:clean
5. Checked that the eth1 interface was removed.
-bash-4.2# foreman-rake interfaces::clean
/usr/share/foreman/lib/foreman.rb:8: warning: already initialized constant Foreman::UUID_REGEXP
/usr/share/foreman/lib/foreman.rb:8: warning: previous definition of UUID_REGEXP was here
/usr/share/foreman/lib/core_extensions.rb:182: warning: already initialized constant ActiveSupport::MessageEncryptor::DEFAULT_CIPHER
/opt/theforeman/tfm-ror51/root/usr/share/gems/gems/activesupport-5.1.6/lib/active_support/message_encryptor.rb:22: warning: previous definition of DEFAULT_CIPHER was here
rake aborted!
Don't know how to build task 'interfaces::clean' (see --tasks)
/opt/rh/rh-ruby24/root/usr/share/gems/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
-bash-4.2# foreman-rake interfaces:clean
/usr/share/foreman/lib/foreman.rb:8: warning: already initialized constant Foreman::UUID_REGEXP
/usr/share/foreman/lib/foreman.rb:8: warning: previous definition of UUID_REGEXP was here
/usr/share/foreman/lib/core_extensions.rb:182: warning: already initialized constant ActiveSupport::MessageEncryptor::DEFAULT_CIPHER
/opt/theforeman/tfm-ror51/root/usr/share/gems/gems/activesupport-5.1.6/lib/active_support/message_encryptor.rb:22: warning: previous definition of DEFAULT_CIPHER was here
Starting ingnored interfaces clean up...
Finished, cleaned 1 interfaces
Check attachment for eth1 not showing up.
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, 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-2018:2927