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.
Ohai,
this is on EL7 nightly, but I think all puma deploys are affected.
My production.log is full of
<pre>
2021-03-05T08:57:04 [I|app|e0cfbd4f] Started GET "/users/login" for 127.0.0.1 at 2021-03-05 08:57:04 +0000
</pre>
Whereas I'd expect to see the real IP address of the remote system here. Apache logs look correct:
<pre>
192.168.122.1 - - [05/Mar/2021:08:57:04 +0000] "GET /users/login HTTP/1.1" 200 1283 "-" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0"
</pre>
The same issue is observed in audits, every audit shows 127.0.0.1 as an IP.
This is of course due to the migration to Puma. There's a more complex fix proposed in this PR which comes with a risk for Katello regressions https://github.com/theforeman/foreman/pull/7960, perhaps we can take a simpler aproach not lowering the security comparing to 6.8 but that needs to be investigated.
I'm raising this with high priority and severity.
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.9 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-2021:1313