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.

Bug 1981517

Summary: [pulp3] When refreshing the Satellite Features via WebUI apache logs show an error dua to 'No such file or directory'.
Product: Red Hat Satellite Reporter: Rudnei Bertol Jr. <rbertolj>
Component: Capsule - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Vladimír Sedmík <vsedmik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.0CC: ahumbe, dhjoshi, ttereshc
Target Milestone: 6.10.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:12:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rudnei Bertol Jr. 2021-07-12 17:52:24 UTC 
Description of problem:

When refreshing the features on Satellite 6.9.3 the apache logs '/var/log/httpd/foreman-ssl_access_ssl.log' show the following API call:

~~~
XXX.XXX.XXX.XXX - - [12/Jul/2021:10:04:50 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:11:05:04 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:12:04:38 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:13:05:00 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:14:04:57 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:15:04:59 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:16:04:56 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:27 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:28 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:28 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
XXX.XXX.XXX.XXX - - [12/Jul/2021:16:21:28 +0200] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"
~~~

And the following errors on '/var/log/httpd/foreman-ssl_error_ssl.log' apache logs.

~~~
[Fri Jul 09 08:39:50.627665 2021] [proxy:error] [pid 11308] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s
[Fri Jul 09 08:39:50.627668 2021] [proxy_http:error] [pid 11308] [client XXX.XXX.XXX.XXX:36230] AH01114: HTTP: failed to make connection to backend: httpd-UDS
[Fri Jul 09 08:39:50.786779 2021] [ssl:warn] [pid 62365] [client XXX.XXX.XXX.XXX:36236] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN'
[Fri Jul 09 08:39:50.787018 2021] [proxy:error] [pid 62365] (2)No such file or directory: AH02454: HTTP: attempt to connect to Unix domain socket /run/pulpcore-api.sock (pulpcore-api) failed
[Fri Jul 09 08:39:50.787030 2021] [proxy:error] [pid 62365] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s
[Fri Jul 09 08:39:50.787033 2021] [proxy_http:error] [pid 62365] [client XXX.XXX.XXX.XXX:36236] AH01114: HTTP: failed to make connection to backend: httpd-UDS
[Fri Jul 09 08:39:50.885699 2021] [ssl:warn] [pid 11016] [client XXX.XXX.XXX.XXX:36240] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN'
[Fri Jul 09 08:39:50.885919 2021] [proxy:error] [pid 11016] (2)No such file or directory: AH02454: HTTP: attempt to connect to Unix domain socket /run/pulpcore-api.sock (pulpcore-api) failed
[Fri Jul 09 08:39:50.885930 2021] [proxy:error] [pid 11016] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s
[Fri Jul 09 08:39:50.885933 2021] [proxy_http:error] [pid 11016] [client XXX.XXX.XXX.XXX:36240] AH01114: HTTP: failed to make connection to backend: httpd-UDS
~~~

Version-Release number of selected component (if applicable):

Satellite 6.9.3

How reproducible:

Go to the Satellite WebUI, Infrastructure > Capsules > Click on the Satellite Host > Actions > Refresh

Steps to Reproduce:
1. Go to the Satellite WebUI
2. Click on "Infrastructure > Capsules > Click on the Satellite Host > Actions > Refresh"
3. Check the logs '/var/log/httpd/foreman-ssl_error_ssl.log' and '/var/log/httpd/foreman-ssl_access_ssl.log'

Actual results:

Customers are seeing errors on the apache logs.

~~~
==> /var/log/httpd/foreman-ssl_access_ssl.log <==
2620:52:0:ab0:6a11:d248:3bfc:a04f - - [12/Jul/2021:13:45:13 -0400] "GET /pulp/api/v3/status/ HTTP/1.1" 503 299 "-" "Ruby"

==> /var/log/httpd/foreman-ssl_error_ssl.log <==
[Mon Jul 12 13:45:13.928693 2021] [ssl:warn] [pid 12341] [client 2620:52:0:ab0:6a11:d248:3bfc:a04f:40690] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN'
[Mon Jul 12 13:45:13.928988 2021] [proxy:error] [pid 12341] (2)No such file or directory: AH02454: HTTP: attempt to connect to Unix domain socket /run/pulpcore-api.sock (pulpcore-api) failed
[Mon Jul 12 13:45:13.929006 2021] [proxy:error] [pid 12341] AH00959: ap_proxy_connect_backend disabling worker for (pulpcore-api) for 60s
[Mon Jul 12 13:45:13.929009 2021] [proxy_http:error] [pid 12341] [client 2620:52:0:ab0:6a11:d248:3bfc:a04f:40690] AH01114: HTTP: failed to make connection to backend: httpd-UDS
~~~

Expected results:


Additional info:
Comment 4 Tanya Tereshchenko 2021-07-23 16:02:21 UTC 
Are you running `content prepare` commands to migrate from pulp 2 to pulp 3? 
Just trying to understand why it is expected for pulp 3 to run.
Comment 5 Tanya Tereshchenko 2021-07-23 16:42:15 UTC 
One theory is that potentially there should be no calls to pulp3 on 6.9 while working with capsules.
Moving to Katello for the initial investigation. Thanks.
Comment 10 errata-xmlrpc 2021-11-16 14:12:34 UTC 
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.10 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:4702
Comment 11 Red Hat Bugzilla 2023-09-15 01:11:19 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days