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:

Assuming ip obfuscation is enabled in insights-client.

If the list of ips passed by insights-client is too long, the ips generated by rh_cloud plugin could result in invalid value (e.g. 10.230.230.300)


How reproducible:

Always.


Steps to Reproduce:
1. Set up a host with insights-client
2. Configure insights client to use ip obfuscation
3. Add 260 ips to /etc/hosts (this is not the only way, but it's quite simple one). We need to generate a long list of ips in obfuscated ips fact.
4. Run insights-client to generate the fact
5. Run subscription-manager to upload the fact to Satellite
6. Generate an rh_cloud report
7. Observe the generated ips

Actual results:

IP record in invalid format (10.230.230.300)

Expected results:

Correct IP record (10.230.231.10)


Additional info:

The version of tfm-rubygem-foreman_rh_cloud from redhat.com is 4.0.31-1.el7sat
Is this the same as foreman_rh_cloud_5.0.32 ?

We have a partner waiting on this fix and applying this would really help.

https://access.redhat.com/errata/RHSA-2022:0790

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 (Moderate: Satellite 6.11 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:5498