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:
It looks like that Satellite struggles to process ansible facts during ansible role execution when target hosts have unusually high amount of ansible facts. Example of such host could be a RHV host that holds a lot of NICs.
How reproducible:
I'd expect this to be reproducible if one has an access to a suitable environment.
More information will follow in my next private comment.
Kind regards,
Jan
What can quickly help is to setup the facts blacklist in Settings. Navigate to Settings -> Provisioning -> Exclude pattern for facts stored in satellite, add more fact names. As you can see in the default value, * wildcard can be used. Looking at the logs, it seems there were around 7k facts. That may not be only caused by multiple NICs. Make sure you don't have ohai installed on the machine. Ansible by default uses multiple fact providers and ohai (facter from chef) is extremely verbose. This can be disabled in ansible.cfg.